Bhiyavudh Suwanchinda wrote:
Dear List,
Hope someone could clarify a few issues for us. We are keen to learn about a portal software solution, based on the JSR 168 spec.
Jetspeed -1 is NOT based on JSR 168. Will Jetspeed 2 be compliant? Does anybody know when the first stable binary release is planned ?
Jetspeed-1 does support JSR 168 via the 'Fusion' option. It is currently only available from a branch on the CVS head named
pre_portalurl_refactor_20041015
JSR 168 support will be a part of the Jetspeed 1.6 release this month (I really really hope)
Pluto is a reference Implemenation of the JSR 168 spec. Could someone clarify what the difference between Jetspeed 2 and Pluto.Pluto is the portlet container that implements the low level details of the Portlet API: the interface contract between portlets and the portal.
Jetspeed is a portal leveraging Pluto as its Portlet container.
We are aware that the desktop customization and aggregation (GUI) is not defined inside of the JSR, with each vendor independently implementing their own GUI solution. To what extent will it therefore be possible to simply install an App based on Jetspeed 2 onto another Portal container.
Portlet Applications written to the Java Portlet spec should run in any Java Portlet compliant portal.
When you say a portlet app 'based on Jetspeed 2' Im not sure what you mean
We have some special portlet applications that run the Jetspeed administration, but they are not meant to be deployed to other portals.
For general portlet applications, there should be no dependencies on Jetspeed.
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773 4646 [mobile] +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
