[Talk:PlutoProposal Talk Page]
Proposal for Pluto ? A Jakarta Subproject
21 January 2003, Stefan Hepper (sthepper@de.ibm.com)
(0) rationale
To enable interoperability between Portlets and Portals, IBM and SUN initiated the JSR 168. This JSR will define a set of APIs for Portal computing addressing the areas of aggregation, personalization, presentation and security. It will define Portlets, the Portlet container behavior, invocation of Portlets, Portlet services, a Portlet window, event model, and other relevant entities and interfaces. For more information see http://jcp.org/en/jsr/detail?id=168.
As part of this JSR a reference implementation of the portlet container, which is the run-time environment of the Portlets, will be created. This reference implementation will be based on the Tomcat subproject.
There are two other projects at Jakarta, which could pick up the reference implementation of the portlet container to leverage that work. One is the JetSpeed portal project and the other one is the Charon proposal. In addition the Apache Cocoon project might also pick up the reference implementation for its portal engine.
The portlet container will be build on top of the Servlet container and JetSpeed can use this container in its particular portal implementation, other persons or companies also could pick up the portlet container reference implementation and use it for their products.
Having Pluto done under Apache would also ensure that there is a tight communication between the developers of the Servlet container, the portlet container, the portal, and the WSRP implementation proposal Charon.
(1) scope of the subproject
The only purpose of this subproject is to create and maintain a reference implementation for the Java Portlet specification as defined in http://jcp.org/jsr/detail/168.jsp. The goal for the reference implementation is to create an independent portlet container that may be plugged into every possible driver, for instance JetSpeed. This project will not create a new portal, but only a reference implementation of a portlet container.
There is an agreement with JetSpeed that the JetSpeed will be based on this portlet container implementation.
(2) identify the initial source from which the subproject is to be populated
The JSR 168 Expert Group has a prototype based on Tomcat, which will be the starting point for the subproject. This prototype will be submitted to Jakarta after the first JSR 168 draft is made public available, which is currently scheduled for end of March.
(3) identify the Jakarta resources to be created
(3.1) mailing list(s) pluto-user pluto-dev
(3.2) CVS repositories jakarta-pluto
(3.3) Bugzilla
(4) identify the initial set of committers
Stefan Hepper (sthepper@de.ibm.com)
Stephan Hesmer (stephan.hesmer@de.ibm.com)
Birga Rick (brick@de.ibm.com)
David Sean Taylor (david@bluesunrise.com)
Glenn R. Golden (ggolden@apache.org)
Alejandro Abdelnur (alejandro.abdelnur@sun.com)
Davanum Srinivas (dims@yahoo.com)
Raphaël Luta (raphael@apache.org)
Carsten Ziegeler (cziegeler@s-und-n.de)
Santiago Gala (sgala@hisitech.com)
Serge Huber (shuber2@jahia.com)
(5) identify apache sponsoring individual
Sam Ruby (rubys@us.ibm.com)