Hi Grigoris,
This is a standard configuration issue which has little to do with Tapestry,
you use a reverse proxy, but also need to have a sticky session and also set
the route/JVMRoute parameter.
In Tomcat you set it on the connector in server.xml (should be similar for
JBoss). This is neede
Finally this solved the problem: I used both of your suggestions:
I replaced ROOT.war with my application and
I set "tapestry.suppress-redirect-from-action-requests" to true
This seems to solve the problem.
Thanks,
Grigoris
On Fri, Aug 1, 2008 at 4:18 PM, Jonathan Barker <[EMAIL PROTECTED]
> wr
I've used a different technique for the apache->jboss connection, but faced
the same problem.
Unless someone else has a better solution, you can replace the ROOT.war in
the JBoss tomcat service with your application.
Jonathan
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL
I've had a similar problem. It's because when Jetty redirects you, it
uses "request.getServerName()" and the request context to create a
complete URL. So if you go to your app at "http://localhost/page";, and
that sends a redirect, Jetty will redirect you to
"http://localhost/whatever";.
The prob
