Torsten - I understand JSR-286 - that tells portlet writers how to
write new-style portlets.
I am curious for those of us who have portals based on Pluto 1.1.x -
we wrote a bunch of code to make Pluto 1.x handle our JSR-168 support
- things like preference store providers, user attribute providers, etc.
I will want to get Sakai to use the Pluto 2.x.x jars instead so our
developers can write JSR-286 portlets in addition to JSR-168 portlets.
I am curious the kinds of new providers we need to build for the Pluto
2.x code. Another way to ask the question is - what kinds of changes
were made to the Pluto out of the box portal's providers ?
I am sure that in time I will look at the code for the pluto reference
portal - but a nice outline of what to look for would be a nice start.
And it is possible that there are relatively few new requirements on
we portals - if all the new stuff like events, etc is all nicely
handled by Pluto 2.x with no need for additional persistence handlers
or what ever - that would be great. But I am guessing that there are
a few new things that we portals must do.
/Chuck
On Dec 7, 2007, at 11:03 AM, Torsten Dettborn wrote:
---BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Chuck,
the specification proposed final version has a list of all changes of
the specification. See PLT.2.6.3 in rev. 30
http://hnsp.inf-bb.uni-jena.de/spec/JSR%202.0%20Spec/PortletSpec_20_noTrackChanges.pdf
Hope it helps you to get an overview
Torsten
