You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Bhiyavudh Suwanchinda <bh...@yahoo.com> on 2004/11/05 18:39:34 UTC
Portlet JSR 168 Specification
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 ?
Pluto is a reference Implemenation of the JSR 168 spec. Could someone clarify what the difference between Jetspeed 2 and Pluto.
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.
I look forward to any replies.
sincerely
bhiyavudh
---------------------------------
Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com/a
Re: Portlet JSR 168 Specification
Posted by David Sean Taylor <da...@bluesunrise.com>.
Bhiyavudh Suwanchinda wrote:
> Hi David,
>
> Thank you for your answers. What I mean about "desktop or user
> customization and aggregation is not fully defined inside of the JSR
> 168", is that, as it was mentioned at the end of the JSR 168
> specification that independent vendor can implement the user
> customization and aggregation in their own way. This difference do
> exist among portal products from SUN, IBM and ORACLE and what is
> currently implement in jetspeed 1 which is coupling with velocity
> template (like how to define portlets layout using menu or tab
> controller inside psml file). What I mean here is that, it is
> totally a different concept on Sun or Websphere or Oracle portal
> server regarding how to implement the user cutomization and
> personalization of the portlets. I beleive there will be a total
> seperation from velocity and turbine framework in the next version of
> jetspeed and a claer and clean framework to provide user
> customization and personalization as already existed on the non-free
> (commercial) products. Apologize for my English, I hope you could
> understand what I am trying to ask here.
>
> Regards,
>
>
There haven't been any efforts thus far to standardize layouts, site
navigations, or decorators.
In the next version of Jetspeed, Jetspeed-2 (first release available
within the month hopefully) we have completely decoupled from Turbine.
However Velocity is still popular amongst both users and developers.
While some layouts and decorators are written in Velocity, others in
JSP. Its up to the layout designer, they are both dispatched in the same
way.
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773 4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: Portlet JSR 168 Specification
Posted by Bhiyavudh Suwanchinda <bh...@yahoo.com>.
Hi David,
Thank you for your answers. What I mean about "desktop or user customization and aggregation is not fully defined inside of the JSR 168", is that, as it was mentioned at the end of the JSR 168 specification that independent vendor can implement the user customization and aggregation in their own way. This difference do exist among portal products from SUN, IBM and ORACLE and what is currently implement in jetspeed 1 which is coupling with velocity template (like how to define portlets layout using menu or tab controller inside psml file). What I mean here is that, it is totally a different concept on Sun or Websphere or Oracle portal server regarding how to implement the user cutomization and personalization of the portlets. I beleive there will be a total seperation from velocity and turbine framework in the next version of jetspeed and a claer and clean framework to provide user customization and personalization as already existed on the non-free (commercial) products.
Apologize for my English, I hope you could understand what I am trying to ask here.
Regards,
David Sean Taylor <da...@bluesunrise.com> wrote:
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
david@bluesunrise.com
[office] +01 707 773 4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
---------------------------------
Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com/a
Re: Portlet JSR 168 Specification
Posted by David Sean Taylor <da...@bluesunrise.com>.
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
david@bluesunrise.com
[office] +01 707 773 4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: Portlet JSR 168 Specification
Posted by Roger Ruttimann <ro...@apache.org>.
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 ?
>
>
J1 is not and J2 fully supports it.
The first J2 release is planned for end of November
>
>Pluto is a reference Implemenation of the JSR 168 spec. Could someone clarify what the difference between Jetspeed 2 and Pluto.
>
>
Jetspeed is the Portal framework with a lot of features (customization,
user, security,..)
>
>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.
>
>
>
The portlets will be portable not the framework. In other words your
business logic implemented in portlets will be runnable on any JSR-168
compliant portals
>I look forward to any replies.
>
>sincerely
>
>bhiyavudh
>
>
>
>---------------------------------
>Do you Yahoo!?
> Check out the new Yahoo! Front Page. www.yahoo.com/a
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org