On Thursday, August 7, 2003, at 07:25 AM, Craig M. Doremus wrote:
Greetings!
I started subscribing to this list after the recent publication of the JSR-168 draft. From what I've seen, there seem to be a number of newbies on this list since the new Portal spec will be an important one in the future of J2EE.
It was my original understanding after what I read on ServerSide and elsewhere that Jetspeed2 would be the JSR-168 reference implementation, but that might not be the case from what I've read here and on jetspeed-user. The rings of Uranus might be black (scientists say that's true), but the relationship between Pluto and Jetspeed2 appears to be cloudy in my mind. Will the real Reference Implemenation please stand up!
Pluto is the real reference implementation. Jetspeed-2 uses Pluto as its default container.
We hope to be able to distribute the Pluto jar with Jetspeed soon.
From what I've read here, you need Pluto to run Jetspeed2 (although Pluto's not available to the general public yet). Can someone explain how Pluto fits into Jetspeed2's architecture. Is there some UML or another diagram that I can take a look at to clarify the relationship between Pluto and Jetspeed2.
We are still waiting on the licensing issues to get sorted out.
Read the spec. It best describers the roles of the portal, container, and portlet applications.
Jetspeed is the portal, Pluto the container.
I had to take six weeks off J2 development, Im back now, and we will all make an effort to write better documentation.
If Pluto is the RI, I assume it will work standalone as a JSR-168 compliant portlet engine. What added value will Jetspeed2 have on top of Pluto?Pluto will not have many portal features. Its not very useful in the real world.
Jetspeed-2 adds the portal features such as customization, sophisticated portlet aggregation, security, registries in the database.
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] +01 707 773-4646 +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
