-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
Pid wrote:
Christopher Schultz wrote:
Bottom line: beware deploying applications inside one another's URI spaces.
Do you mean 'inside' as in the (expected) outcome of
app1.war
app1#part2.war
It's worse than that, because Apache httpd
Christopher Schultz wrote:
Pid,
Pid wrote:
Stefano Nichele wrote:
Hi All,
I have a strange (for me?) requirement for my application.
Basically I have webapp A deployed in Tomcat A and webpp B deployed in
Tomcat B. webappA is the main webapplication that provides the main
web page to the
Stefano Nichele wrote:
Hi All,
I have a strange (for me?) requirement for my application.
Basically I have webapp A deployed in Tomcat A and webpp B deployed in
Tomcat B. webappA is the main webapplication that provides the main
web page to the the browser. That page contains an IFrame that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
Pid wrote:
Stefano Nichele wrote:
Hi All,
I have a strange (for me?) requirement for my application.
Basically I have webapp A deployed in Tomcat A and webpp B deployed in
Tomcat B. webappA is the main webapplication that provides the main
Actually, you should have the path set in the cookie, too.
Verify looking at your browser cookies.
Be sure not to have something like:
emptySessionPath=true
in the connector definition in server.xml
(usually we have to set it to true because when not set or set to false we have
errors due to
