Hi John,
In order to narrow down the search, have you tried the 1.5.2 webapp in your
previous app server etc. ?
That way you could know if Stripes is the problem, or if it's your app
server...
Cheers
Remi
2011/5/4 Newman, John W newma...@d3onc.com
No sir, just the core jar .. we’re not
Hello,
The ~30min delay may be a clue. Does it match your HTTP Session
timeout (30min by default on Tomcat) ? You could control what's being
stored in your HTTP Session...
Gérald
2011/5/4 Newman, John W newma...@d3onc.com:
No sir, just the core jar .. we’re not really doing anything too wild..
Daniil,
There was a thread in February IIRC on this and solutions were
mentioned. End-to-end UTF-8 support requires multiple layers.
If you are looking at simply posting data and having it encoded in
UTF-8 then AFAIK Stripes already performs
request.setCharacterEncoding(...) passing in the
