Hi guys,
See inline comments below.
Ate
David Sean Taylor wrote:
On Feb 11, 2009, at 10:22 AM, Eric Dalquist wrote:
I think it is likely pretty close as far as module requirements go to
1.1. For 1.1 uPortal depends on (all of which end up in shared/lib in
Tomcat)
pluto-container
pluto-descriptor-api
pluto-descriptor-impl
pluto-taglib
And for deployment we depend on
pluto-ant-tasks
pluto-util
I'm actually curious about the status of trunk and where it is with
286 spec compliance and general completeness. I'm looking at upgrading
uPortal to Pluto 2.0 to get JSR-286 support this summer and it would
be good to know what is left to be done.
Ate and I are actively working on getting Jetspeed compliant with the
2.0 standard and operating with Pluto 2.0. In Jetspeed, we are
implementing the new JSR-286 feature set like events, filters. We have
some refactoring to go back into Pluto that we have been discussing just
today.
Ate, could you please discuss your plans for refactoring the request
wrappers? thanks
Yes, I'm about to complete a rather lengthy message to this list describing several Pluto SPI and implementation issues which I think
require fixing before we can finalize the Pluto 2.0 container for embedding in portals like Jetspeed-2 or others, as well as before we can
release Pluto 2.0.
One of these is a required refactoring of the request/response wrappers as
David mentioned above, but also several others.
I'll send this issue inventory list and proposed solutions for them shortly.
Regards,
Ate
