You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by CD...@hannaford.com on 2006/08/05 00:48:56 UTC
JSR-286 Early Draft 1 available for review
The JSR-286 (Portlet 2.0) Early Draft 1 has been released by the Java
Community Process. It can be found at:
http://jcp.org/aboutJava/communityprocess/edr/jsr286/. According to that
page:
"This first draft does not contain all the functionality that the JSR 286
EG considers for this JSR, but mainly supports the features introduced
with Web Service for Remote Portlets (WSRP) V 2.0 defined at OASIS and
thus the JSR 286 EG seeks feedback these features. Additional features
will be introduced with a second early draft."
Note that the PDF 'Without Track Changes' is broken right now. The other
PDF has color highlighting new text in the document.
According to PLT.2.6 of the Early Draft:
The major new features of version 2.0 include:
* Events -- enabling portlet to send and receive events and perform state
changes or
send further events as result of processing an event.
* Shared session attributes -- allowing portlets to share session
attributes beyond
the current web application.
* Shared render parameters -- allowing portlets to share render parameters
with
other portlets.
* Resource serving -- provides ability for a portlet to serve a resource.
* Portlet filter -- allowing on the fly transformations of information in
both the
request to and the response from a portlet
The closing date for this early draft review is Sept 1. Please send your
comments to jsr-286-comments@jcp.org.
Re: JSR-286 Early Draft 1 available for review
Posted by "David H. DeWolf" <dd...@apache.org>.
I Totally agree. We need a push towards 1.1 final.
In regards to 286 and the next generation of Pluto, I guess my point is
simply that I'd like to see our community share some ideas and innovate
here. I think it would be a good way to energize the community. In
addition, as you hinted, it was difficult to pick up support for Pluto
when it was originally "dumped". I'd really like to avoid that again.
The bottom line is that I'm excited about the work that the Univ of Jena
is doing and hope that we can work together with them on it. I'm 100%
behind their effort.
David
Carsten Ziegeler wrote:
> David H. DeWolf wrote:
>
>> Ulrich, can you help us get on board with what your team is doing and make
>> sure that we're able to develop as a community (I assume that is the
>> intention since the project overview states "This project is organised by
>> apache").
>>
>>
> I think either the development/discussion takes place here or that
> page/project has to be corrected. Currently Apache has nothing to do
> with it :( (And in the end it is up to us to accept a possible code
> donation).
>
>
>> Craig et al,
>>
>> Either way, I think we should begin to collaborate regarding 286. I think
>> that this type of new development is a good opportunity to energize our
>> community. Even if for some reason the Univ of Jena does not develop from
>> asf svn, we should beging work on our own version.
>>
>>
> I'm not against this, but I'm not sure if this is a good idea either :)
> Personally, I would love to have a final release of 1.1 first (even if
> perhaps not all bugs/problems are fixed).
>
> Carsten
>
Re: JSR-286 Early Draft 1 available for review
Posted by Carsten Ziegeler <cz...@apache.org>.
David H. DeWolf wrote:
> Ulrich, can you help us get on board with what your team is doing and make
> sure that we're able to develop as a community (I assume that is the
> intention since the project overview states "This project is organised by
> apache").
>
I think either the development/discussion takes place here or that
page/project has to be corrected. Currently Apache has nothing to do
with it :( (And in the end it is up to us to accept a possible code
donation).
> Craig et al,
>
> Either way, I think we should begin to collaborate regarding 286. I think
> that this type of new development is a good opportunity to energize our
> community. Even if for some reason the Univ of Jena does not develop from
> asf svn, we should beging work on our own version.
>
I'm not against this, but I'm not sure if this is a good idea either :)
Personally, I would love to have a final release of 1.1 first (even if
perhaps not all bugs/problems are fixed).
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
RE: JSR-286 Early Draft 1 available for review
Posted by "David H. DeWolf" <dd...@apache.org>.
Ulrich, can you help us get on board with what your team is doing and make
sure that we're able to develop as a community (I assume that is the
intention since the project overview states "This project is organised by
apache").
Craig et al,
Either way, I think we should begin to collaborate regarding 286. I think
that this type of new development is a good opportunity to energize our
community. Even if for some reason the Univ of Jena does not develop from
asf svn, we should beging work on our own version.
David
> -----Original Message-----
> From: Craig Doremus [mailto:cdoremus@apache.org]
> Sent: Thursday, August 10, 2006 7:43 AM
> To: pluto-dev@portals.apache.org
> Subject: Re: JSR-286 Early Draft 1 available for review
>
> Hi David:
>
> As you know, IBM has funded a group at the Univ of Jena in
> Germany to work on the JSR-286 RI to be based at Apache-Pluto
> (see http://hnsp.inf-bb.uni-jena.de/pluto/). Stephan has told
> me they have begun work on this project based on a fork of
> Pluto 1.1. We need to encourage them to move this work into
> the Pluto SVN repository as soon as possible so the rest of
> us can also contribute. I believe that Ulrich Küster, a
> member of this group, is a Pluto committer.
> /Craig
>
>
> >Now that this has been released we can begin to consider how to
> >implement those things that are included in the draft. Anyone who's
> >interested should start to think these things through and
> share ideas
> >on this list. Also, whenever we're ready to start we should create
> >another branch to work on - probably pluto-2.0.
> >
> >
> >David
> >
> >
> > _____
> >
> >From: CDoremus@hannaford.com [mailto:CDoremus@hannaford.com]
> >Sent: Friday, August 04, 2006 6:49 PM
> >To: pluto-users@portals.apache.org; pluto-dev@portals.apache.org
> >Subject: JSR-286 Early Draft 1 available for review
> >
> >
> >
> >The JSR-286 (Portlet 2.0) Early Draft 1 has been released by
> the Java
> >Community Process. It can be found at:
> >http://jcp.org/aboutJava/communityprocess/edr/jsr286/. According to
> >that
> >page:
> >"This first draft does not contain all the functionality
> that the JSR
> >286 EG considers for this JSR, but mainly supports the features
> >introduced with Web Service for Remote Portlets (WSRP) V 2.0
> defined at
> >OASIS and thus the JSR
> >286 EG seeks feedback these features. Additional features will be
> >introduced with a second early draft."
> >
> >Note that the PDF 'Without Track Changes' is broken right now. The
> >other PDF has color highlighting new text in the document.
> >
> >According to PLT.2.6 of the Early Draft:
> >The major new features of version 2.0 include:
> >* Events -- enabling portlet to send and receive events and perform
> >state changes or send further events as result of processing
> an event.
> >* Shared session attributes -- allowing portlets to share session
> >attributes beyond the current web application.
> >* Shared render parameters -- allowing portlets to share render
> >parameters with other portlets.
> >* Resource serving -- provides ability for a portlet to
> serve a resource.
> >* Portlet filter -- allowing on the fly transformations of
> information
> >in both the request to and the response from a portlet
> >
> >The closing date for this early draft review is Sept 1. Please send
> >your comments to jsr-286-comments@jcp.org.
> >
> >
> >
> >
>
Re: JSR-286 Early Draft 1 available for review
Posted by Craig Doremus <cd...@apache.org>.
Hi David:
As you know, IBM has funded a group at the Univ of Jena in Germany to
work on the JSR-286 RI to be based at Apache-Pluto (see
http://hnsp.inf-bb.uni-jena.de/pluto/). Stephan has told me they have
begun work on this project based on a fork of Pluto 1.1. We need to
encourage them to move this work into the Pluto SVN repository as soon
as possible so the rest of us can also contribute. I believe that Ulrich
Küster, a member of this group, is a Pluto committer.
/Craig
>Now that this has been released we can begin to consider how to implement
>those things that are included in the draft. Anyone who's interested should
>start to think these things through and share ideas on this list. Also,
>whenever we're ready to start we should create another branch to work on -
>probably pluto-2.0.
>
>
>David
>
>
> _____
>
>From: CDoremus@hannaford.com [mailto:CDoremus@hannaford.com]
>Sent: Friday, August 04, 2006 6:49 PM
>To: pluto-users@portals.apache.org; pluto-dev@portals.apache.org
>Subject: JSR-286 Early Draft 1 available for review
>
>
>
>The JSR-286 (Portlet 2.0) Early Draft 1 has been released by the Java
>Community Process. It can be found at:
>http://jcp.org/aboutJava/communityprocess/edr/jsr286/. According to that
>page:
>"This first draft does not contain all the functionality that the JSR 286 EG
>considers for this JSR, but mainly supports the features introduced with Web
>Service for Remote Portlets (WSRP) V 2.0 defined at OASIS and thus the JSR
>286 EG seeks feedback these features. Additional features will be introduced
>with a second early draft."
>
>Note that the PDF 'Without Track Changes' is broken right now. The other PDF
>has color highlighting new text in the document.
>
>According to PLT.2.6 of the Early Draft:
>The major new features of version 2.0 include:
>* Events -- enabling portlet to send and receive events and perform state
>changes or
>send further events as result of processing an event.
>* Shared session attributes -- allowing portlets to share session attributes
>beyond
>the current web application.
>* Shared render parameters -- allowing portlets to share render parameters
>with
>other portlets.
>* Resource serving -- provides ability for a portlet to serve a resource.
>* Portlet filter -- allowing on the fly transformations of information in
>both the
>request to and the response from a portlet
>
>The closing date for this early draft review is Sept 1. Please send your
>comments to jsr-286-comments@jcp.org.
>
>
>
>
RE: JSR-286 Early Draft 1 available for review
Posted by "David H. DeWolf" <dd...@apache.org>.
Now that this has been released we can begin to consider how to implement
those things that are included in the draft. Anyone who's interested should
start to think these things through and share ideas on this list. Also,
whenever we're ready to start we should create another branch to work on -
probably pluto-2.0.
David
_____
From: CDoremus@hannaford.com [mailto:CDoremus@hannaford.com]
Sent: Friday, August 04, 2006 6:49 PM
To: pluto-users@portals.apache.org; pluto-dev@portals.apache.org
Subject: JSR-286 Early Draft 1 available for review
The JSR-286 (Portlet 2.0) Early Draft 1 has been released by the Java
Community Process. It can be found at:
http://jcp.org/aboutJava/communityprocess/edr/jsr286/. According to that
page:
"This first draft does not contain all the functionality that the JSR 286 EG
considers for this JSR, but mainly supports the features introduced with Web
Service for Remote Portlets (WSRP) V 2.0 defined at OASIS and thus the JSR
286 EG seeks feedback these features. Additional features will be introduced
with a second early draft."
Note that the PDF 'Without Track Changes' is broken right now. The other PDF
has color highlighting new text in the document.
According to PLT.2.6 of the Early Draft:
The major new features of version 2.0 include:
* Events -- enabling portlet to send and receive events and perform state
changes or
send further events as result of processing an event.
* Shared session attributes -- allowing portlets to share session attributes
beyond
the current web application.
* Shared render parameters -- allowing portlets to share render parameters
with
other portlets.
* Resource serving -- provides ability for a portlet to serve a resource.
* Portlet filter -- allowing on the fly transformations of information in
both the
request to and the response from a portlet
The closing date for this early draft review is Sept 1. Please send your
comments to jsr-286-comments@jcp.org.