Not to scare you, but we've been upgrading our Tapestry 4 app to 5 for
about 2 1/2 years now. We're still not done. I honestly don't see how any
sort of automatic migration could work. T5 is fundamentally so much
different from the conversion of Hivemind XML to Java-defined IOC service,
to the much heavier use of convention over configuration for connecting
markup to Java, etc. etc.

We have treated this upgrade as a chance to re-evaluate the functionality
in our existing app and rebuild it better in T5. The fact that the T4 and
T5 jars do not collide on the classpath is very convenient. We have been
running them together on the same JVM throughout the transition and it is
not terribly difficult to build mechanisms for communicating between
T4<->T5 as services and pages get converted.

I suppose you could try to do a more direct translation of the
functionality, but why would you want to? The ajax capabilities are so much
better in T5, I think it is well worth taking a second look at how your app
functions and think more in terms of Zones, utilizing
prototype/scriptaculous/jquery/yui/extjs more, etc.

Good luck!

Ben

2012/1/31 Gavin Lei <[email protected]>

> Hi Guys,
>
> We have a some kind of *huge* project which built on Tapestry 4
> started years ago. Now we know Tapestry 5 is more convenient and more
> powerful than 4, and we want to change our Tapestry 4 version to 5.
> If we do these things manually, i think it will cost use more than
> half a year, as it is really a complex project.
>
> So, problems come, do you think it is possible for us to build a tool
> that can convert Tapestry 4 to 5 automatic. If so, i think this tool
> will help many people and save much developers' time. I am not very
> sure of the feasibility things, how do you think of it ? Thank you
>
> --
> ---------------------------------
> Best Regards
> Gavin Lei (雷银)
> Email: [email protected]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to