Migration to Jetspeed from a straight Turbine app

[Bruce Altner <ba...@hq.nasa.gov>]

Greetings;

We're about midway through Phase 1 development of a portal application 
based on Turbine 2.1/Velocity. A new requirement to make this compliant 
with the portlet standard that is on the horizon in 2003 has triggered 
renewed interest in Jetspeed as a portal framework to replace the custom 
one we've built in-house. Does anyone have experience migrating a Turbine 
application to the Jetspeed framework? Because of the close relationship 
between Turbine and Jetspeed one might expect that this shouldn't be too 
difficult but life is never that simple and I'm looking for the hidden 
quicksand. I'd love to hear from anyone who has survived such a journey.

Thanks, in advance.
Bruce


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: Migration to Jetspeed from a straight Turbine app

[David Sean Taylor <da...@bluesunrise.com>]

> -----Original Message-----
> From: Bruce Altner [mailto:baltner@hq.nasa.gov]
> Sent: Tuesday, November 12, 2002 12:32 PM
> To: Jetspeed Users List
> Cc: nathan Shaw; Colin Enger
> Subject: Migration to Jetspeed from a straight Turbine app
>
>
> Greetings;
>
> We're about midway through Phase 1 development of a portal application
> based on Turbine 2.1/Velocity. A new requirement to make this compliant
> with the portlet standard that is on the horizon in 2003 has triggered
> renewed interest in Jetspeed as a portal framework to replace the custom
> one we've built in-house. Does anyone have experience migrating a Turbine
> application to the Jetspeed framework? Because of the close relationship
> between Turbine and Jetspeed one might expect that this shouldn't be too
> difficult but life is never that simple and I'm looking for the hidden
> quicksand. I'd love to hear from anyone who has survived such a journey.
>

Jetspeed is a Turbine application, and we do make use of Velocity
extensively.
So it should be easy to convert things like Turbine actions to
VelocityPortlet actions, or associating Velocity screens with portlets
should be painless.



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>