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!
I can also report 4 production systems running on Server Java 7 (The new
option, server jdk) and tomcats.
Ville
-Alkuperäinen viesti-
Lähettäjä: Bob Harner [mailto:bobhar...@gmail.com]
Lähetetty: 7. maaliskuuta 2014 15:34
Vastaanottaja: Tapestry users
Aihe: Re: Persist object fails
I
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" wrote:
> Tapestry uses Servlet API to persist data, so if they are not persisted,
>
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 c
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 @Ses
