I migrated a pretty large application from 4 to 5. It's been a while and I perhaps I don't remember all the pain but I don't recall it being that difficult. First of all Tapestry 5 is much nicer to use than 4 but shares many of the same ideas. The basic structure is the same you have pages with templates and services. The first thing you'll want to do is build a Tap5 service that allows access to the Tap4 session. I think the next thing I did was rework my Tap4 services in a way they could be used as both Tap5 and Tap4 services. Next pick a page and convert it. We converted all our non public pages first. The biggest issue will be maintaining a similar look and feel between old and new pages.
We also switched from ant to maven when we converted. I think it took us a few months to do it but it was not really that disruptive. Since it's possible to run both in the same web app it's not an all or nothing proposition. Converting the non public pages first will allow you to get comfortable with Tap5 without too much risk. As I recall most of the services did not require much work to convert. Pages and components require more but they are not that bad. Good luck On Friday, June 24, 2016, Thiago H de Paula Figueiredo <thiag...@gmail.com> wrote: > On Fri, 24 Jun 2016 00:18:04 -0300, Mukesh Chandra < > mukesh.chan...@opensolutions.com> wrote: > > So they can share the session? >> > > Yes. They're in the same webapp, same context. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
