Tapestry gurus here may correct me, but I don't see a big problem having a mixed JSP/Tapestry application for the period of conversion. Tapestry is using the same underlying framework based on Servlet Spec, so all the session and request data will be easily shared between JSP and Tapestry components.
I can see two issues thay need to be addressed: 1. Hyperlinking between the two can get hairy, but probably not much worse than it is in standalone JSP. 2. There maybe some extra steps that will need to be done on the Tapestry side to communicate its visit objects to JSP. Andrus > > We have a fairly large site that was built using JSP (before I was > here). However, we are about to change out the "second half" of our > pages (order checkout pages). I was wondering if it is possible (and how > painful) to switch to Tapestry for our last set of pages. We have info > in session and request (order info) that would need to carry through to > the Tapestry pages. > > Is Tapestry all or nothing? How can we start moving to Tapestry? > > Thanks, > Joel Trunick > http://www.smartprice.com/ ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
