Thank you all for your answers.
After querying for the jsessionid value it is found that we have a new value
per request. And that seems to break the persist mechanism at the tomcat level.
We will go for a solution to change this behavior. And check afterwards.
Thank you all!
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
