The Java Community Process(SM) Program - JSRs: Java Specification Requests. Stage. Access. Start. Finish. Final Release Download page. Oct, 2. 00. 3 Final Approval Ballot View results. Sep, 2. 00. 30. 6 Oct, 2. Proposed Final Draft 2. Download page. 08 Sep, 2. Status: Final JCP version in use: 2.1 Java Specification Participation Agreement version in use: 1.0 Description: To enable interoperability between Portlets and. Oracle Technology Network is the ultimate, complete, and authoritative source of technical information and learning about Java. General Information about FreeTTS. Introduction. FreeTTS is a speech synthesis system written entirely in the Java TM programming language. It is based upon Flite. Java SE Java SE 8 Java SE 7 Java SE 6 Java SE 5 Java SE 1.4 Java SE 1.3 Java SE 1.2 Java SE 1.1 JRockit Family Java SE Tutorials JDK 1.3 Documentation JDK 1.4.2. 2: Boundary-Scan API: Description: This API targeted the JavaCard TM platform so as to allow it to be usable on all available Java TM virtual machines from the very. Latest News. Silk Test, Silk Performer, Silk Central 新バージョン17.0をリリース; Micro Focus Visual COBOL 製品に Linux on Powerのサポートを追加. Java Management Extensions (JMX) is a Java technology that supplies tools for managing and monitoring applications, system objects, devices (such as printers) and. Proposed Final Draft Download page. Aug, 2. 00. 3 Public Review Download page. Jul, 2. 00. 31. 6 Aug, 2. Community Draft Ballot View results. Jun, 2. 00. 32. 3 Jun, 2. Community Review Login page. Apr, 2. 00. 32. 3 Jun, 2. Expert Group Formation 1. Feb, 2. 00. 22. 1 Aug, 2. JSR Review Ballot View results. Jan, 2. 00. 21. 1 Feb, 2. Status: Final. JCP version in use: 2. Java Specification Participation Agreement version in use: 1. Description: To enable interoperability between Portlets and Portals, this specification will define a set of APIs for Portal computing addressing the areas of aggregation, personalization, presentation and security. Please direct comments on this JSR to the Spec Lead(s). The following sections of the JSR have updated from the original request. Maintenance Lead: Martin Scott Nicklus. E- Mail Address: scott. Telephone Number: +4. Fax Number: +4. 9- 7. HP has decided to cede its place on the Expert Group to TIBCO. Supporting this JSR: Accenture. Apache Software Foundation. BEABoeing. Borland. Bowstreet. Cap Gemini Ernst & Young. Citrix. Computer Associates. Core. Media. Daimler. Chrysler. Documentum. Enformia Ltd. Hewlett- Packard. Interwoven. Macromedia. Mc. Donald Bradley. Novell. Oracle. Plumtree. SAPSybase. Tarantella, Inc. Vignette. 2. 1. 1 Please describe the anticipated schedule for the development of this. Community Review: 0. Public Review: 0. Release: 0. 8/0. 33. Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available. Different implementations are available today, the following list enumerates some of them. Apache Software Foundation: Jakarta Jet. Speed 1. 3. Jet. Speed home page: http: //jakarta. Jet. Speed Portlet API: http: //cvs. API/. BEA: Web Logic Portal 4. IBM: Web. Sphere Portal 2. Planet: i. Planet Portal Server 3. Oracle: Oracle 9i Portal http: //www. SAP Portal: http: //www. Epicentric portal: http: //www. Identification |. Request |. Contributions. Section 1. Identification. Submitting Member: IBM & Sun Microsystems, Inc. Name of Contact Person: Adam Abramski & Thomas Schaeck. E- Mail Address: adam. Telephone Number: +1 4. Fax Number: +1 4. Specification Lead: Alejandro Abdelnur, Stefan Hepper. E- Mail Address: alejandro. Telephone Number: +1 4. Fax Number: +1 4. Initial Expert Group Membership: Apache Software Foundation. BEAIBMSun Microsystems. Supporting this JSR: Accenture. Apache Software Foundation. BEABoeing. Borland. Bowstreet. Cap Gemini Ernst & Young. Citrix. Daimler. Chrysler. Documentum. Enformia Ltd. Epicentric. Hewlett- Packard. Interwoven. Macromedia. Mc. Donald Bradley. Oracle. Plumtree. SAPSilverstream. Sybase. Tarantella, Inc. Vignette. NOTE that this information has been updated from the original JSR. Section 2: Request. Please describe the proposed Specification. The Portlet specification will define a Portlet API that provides means for aggregating several content sources and applications front ends. It will also address how the security and personalization is handled. Portlets are web components - like Servlets- specifically designed to be aggregated in the context of a composite page. Usually, many Portlets are invoked to in the single request of a Portal page. Each Portlet produces a fragment of markup that it s combined with the markup of other Portlets, all within the Portal page markup. The Portlet specification will define the different components for Portal Computing, their interaction, lifecycle and semantics. These components will comprise - but they will not be restricted to- : Portlets, Deployment descriptor, Portlet APIs. In addition, APIs for vendor extensions, APIs for security, user customization and layout management will be considered. Also, it will define the minimum set of possible window states for a Portlet such as normal, minimized, maximized, etc.- , the valid state transitions and Portlet modes (such as view, edit, help, configure) per markup language. This first version of the Portlet specification will concentrate in the following design goals. Client agnostic. Support for multiple types of clients (multi- device). Simple Portlet API. Support for Localization and Internationalization. Hot deployment and re- deployment of Portal applications. Declarative security (same as to the mechanism found in Servlet and EJB specs). Architected to support remote execution of Portlets. The Portlet specification will be based on the Servlet specification. It is envisioned that the developer API will be similar to the Servlet API. The Portlet specification will restrict the use of functions provided by the Servlet API to a subset that makes sense for components providing fragments of a markup page. Portlets would be able to obtain from their context - via the Portlet API- functions like access to user profile information for the current user, participation in the portal window and action event model, access to web client information, sharing of information with other Portlets and a standard way of storing and retrieving per- user/per- instance Portlet data persistently. The API will provide a URL- rewriting mechanism for creating links to trigger actions within a Portlet without requiring knowledge on how URLs are structured in the particular web application. Portlets would be grouped in a Portal Application by bundling them in a single WAR with a Portlet deployment descriptor file. In addition, the API will provide a mean for sharing data among Portlets of the same Portal Application. Like the Servlet specification, the Portlet specification will allow access to Enterprise Information Systems without imposing restrictions on the type of protocols. It is an important goal that the design of the Portlet specification would allow implementations to support remote Portlet execution. This design would not address the transport protocol for the remote execution of Portlets, leaving to the specific Portal implementations the support for Portlet remote execution. For example, a proxy Portlet could be used to invoke a remote Portlet. The Expert group will consider functionality such as support for, parallel execution of Portlets within a single user request, logging, security and personalization. The Expert group will decide if the specification should include a set of specialized Portlet implementations for common tasks such as syndication (RSS), HTML scrapper, Web Services access, etc. The Expert Group will evaluate defining a Credential mapping service to allow the Portal application to access resources in other applications not supporting the notion of distributed sessions- on behalf of user. It is understood that the subject of this JSR is already being addressed by Open Source projects and products from different vendors. The Objective of this JSR is to create a standard for Java Portal Applications, which will help unifying a fragmented area. The expert group will ensure this specification draws appropriately from such projects and products and that it will be based on open standards. What is the target Java platform? A Java extension for the J2. EE 1. 4 platform. What need of the Java community will be addressed by the proposed specification? This specification will establish a standard API for creating Portlets, thus avoiding locking in Portal developers in a specific implementation and allowing Portlets developers to reach a wider audience while reducing their development efforts. The Portlet specification is required to achieve interoperability between Portlets and Java- based Portal servers or other web applications that implement the specification. The goal is to allow Portlets to be packaged into WAR files and deployed in a standard way on any server implementing the specification. Why isn't this need met by existing specifications? While the Servlet/JSP specifications define an include mechanism for aggregating Servlets and JSPs, they do not define the Desktop metaphor where this aggregation happens. Neither the Servlet/JSP specifications define the possible states and transitions of an included Servlet or JSP, or how the state of one Servlet or JSP affects the display of the other included Servlets or JSPs. In addition, The Servlet/JSP specifications do not define a personalization interface or the idea of persisting the personalization information. Furthermore, the Servlet specification does not define URL- rewriting functions to allow the creation of links and actions targeted to a specific form within the fragment of a page (Portlet markup fragment). The Java Server Faces (JSR 1. MVC based, Web GUI framework focusing on the UI components (input fields, lists, buttons, etc.) and their event model. However, it does not address aggregation, security and personalization. Please give a short description of the underlying technology or technologies: The Portlet specification will be designed leveraging the following technologies: XML, JAXP, Servlet/JSP, JAAS and other J2. EE technologies. For example, a JSP tag library extension or Java Server Faces implementation could be used by a Portlet developer to render the Portlet s content. In addition, a JSP tag library extension or Java Server Faces could be used by a Portal vendor to implement the rendering of the Portal page. For a description of the Portlet technology, refer to section 2. Is there a proposed package name for the API Specification? Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of? No. 2. 8 Are there any security issues that cannot be addressed by the current security model? No. 2. 9 Are there any internationalization or localization issues?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2017
Categories |