Migrating a full blown app from Turbine to Struts (Is it really possible???)

[R Raghavan <rr...@novell.com>]

Dear all,
      We have a full blown app written based on the core Velocity &
Turbine model.
I have a couple of questions?

1. is it really possible to migrate this app to a struts framework? if
so what complications needs to be faced?

2. If not? Is it possible to start the app from turbine itself..and for
the current and future modules use sturts?
           2.1 if this is possible...can we hot link the new modules
running on sturts  from the app running turbine.
           2.2 What will happen to the session exchange and
authentication issues.?
           2.3 Do we have to use two different servers or can this be
done using the same server?

Thanks
Apologies if this issue is already discussed.
regds,
R.Raghavan

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Migrating a full blown app from Turbine to Struts (Is it really possible???)

[Laurie Harper <la...@holoweb.net>]

R Raghavan wrote:
> Dear all,
>       We have a full blown app written based on the core Velocity &
> Turbine model.
> I have a couple of questions?
> 
> 1. is it really possible to migrate this app to a struts framework? if
> so what complications needs to be faced?
> 
> 2. If not? Is it possible to start the app from turbine itself..and for
> the current and future modules use sturts?
>            2.1 if this is possible...can we hot link the new modules
> running on sturts  from the app running turbine.
>            2.2 What will happen to the session exchange and
> authentication issues.?
>            2.3 Do we have to use two different servers or can this be
> done using the same server?
> 
> Thanks
> Apologies if this issue is already discussed.
> regds,
> R.Raghavan

It's been years since I looked at Turbine so take what follows with a 
grain of salt, but... I would guess that migrating the entire app to 
Struts would be a fairly big job. From what I can remember, the Turbine 
processing model is substantially different from Struts.

Getting the Struts framework to coexist in the same, existing web 
application, on the other hand, may be possible. You would then be able 
to develop new modules using Struts while still running your existing 
Turbine based code along side. Struts can use any view-layer technology 
so, at least in theory, your new Struts-based code should be able to 
forward requests to your old Turbine based views when needed. How (or 
if) you could get Turbine to forward control to Struts, though, I don't 
know.

Likely you would have to write some 'glue' code to make your 
Struts-based code aware of certain Turbine-specifics such as 
authentication. Again, this sounds like it should be possible in theory. 
That would depend on how open the relevant Turbine APIs are.

My suggestion would be to try a small prototyping experiment: try to get 
Struts up and running in your existing app; get a few Struts-only pages 
working; then explore the integration issues -- going from a 
Struts-based page to a Turbine-based page and vica versa, unifying 
authentication management across both frameworks, etc.

L.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org