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! >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. 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? Thanks, in advance, for your help in lifting the cloud from my mind (Maybe I just need another dose of caffeine;). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
