I know of many cases of Tapestry 5.3.x web apps running on Java 1.7 and Tomcat in production. No problems, as long as the version of Tomcat chosen is Java 1.7-compatible. On Mar 6, 2014 5:28 PM, "Cezary Biernacki" <cezary...@gmail.com> wrote:
> Tapestry uses Servlet API to persist data, so if they are not persisted, > something wrong is with your Tomcat configuration. I would first check if > JSESSIONID cookies are generated properly and they stay unchanged in a > single session (or alternatively ';jsessionid=' is added to URLs). Then I > would check Tomcat configuration and Tomcat logs. See how your Tomcat is > configured to store sessions. If you use load balancing or put the Tomcat > instance behind a reverse proxy, I would recommend checking how they are > configured. > > If you would still could not solve your problem, I recommend writing a very > simple servlet without Tapestry or any other framework, with simple session > related test, and see if it works correctly on your new installation. If it > would not work too, try to get help on some Tomcat related forum. > > I migrated a Tapestry 5.3 application from Java 6 to Java 7 without any > changes, though I have not used Tomcat. > > Best regards, > Cezary > > > > > On Wed, Mar 5, 2014 at 5:05 PM, Trimech, Fethi <fethi.trim...@leoni.com > >wrote: > > > Hi Tapestry users, > > > > > > > > We are currently migrating our tapestry application to a new server using > > java 1.7. the application was running smoothly until this migration where > > most the features in the application broke down. After analysis we found > > out that all objects annotated with @Persist and @SessionState are no > > longer persisted. > > > > > > > > btw: > > > > same Tomcat version > > > > same OS > > > > using tapetsry 5.3.6 and related jars. > > > > (gave a try to 5.3.7 but also failed) > > > > > > > > does it have todo with the java version or something else? any hint would > > be of great help! > > > > > > > > Thanks! > > > > >
