Posted By:
Wayne_Andersen
Posted On:
Thursday, February 5, 2004 07:31 AM
I am deploying two apps to a single server they both are configured the same but with different context ie. http://localhost:8080/webapp1 http://localhost:8080/webapp2 Both work perfectly by themselves, but if I have both deployed at the same time all all request to any .do page are handled by the first installed webapp context. For example my index.jsp page forwards to a /logon.do global forward. I can deploy the first webapp thennavigate to http://localhost:8080/webapp1 and it returns the correct login page. I then deploy the second app and navigate to http://localhost:8080/webapp2, but I get the login page for the first app. I have a in my login page and it
More>>
I am deploying two apps to a single server they both are configured the same but with different context ie.
http://localhost:8080/webapp1
http://localhost:8080/webapp2
Both work perfectly by themselves, but if I have both deployed at the same time all all request to any .do page are handled by the first installed webapp context.
For example my index.jsp page forwards to a /logon.do global forward. I can deploy the first webapp thennavigate to http://localhost:8080/webapp1 and it returns the correct login page.
I then deploy the second app and navigate to http://localhost:8080/webapp2, but I get the login page for the first app.
I have a
in my login page and it always show the correct context but the page is definately the login page from the other context.
Do I have to configure strust so that it recognizes a particular context?
