The web server fronts the app server. Locally, during development, I call directly against the app server. For deployment, I must go through a web server. It sends requests to <root>/somepath to the root path of my app server. Thus, the actual path to my resources is <root>/somepath/myWebApp/whateverresource. (FWIW, I deploy as an expanded war, though I can change that if it fixes this problem.)
Works ok until you get the Struts url rewriting which doesn't know about "somepath." I'm hoping there's a way to make Struts know about "somepath." Thanks, - Mike -----Original Message----- From: Jamie M. Guillemette [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 09, 2003 10:00 AM To: Struts Users Mailing List Subject: Re: When the Struts webapp is not at the root of the server Hi Mike, Your webapp would be built as if it was running from <root>/weapp/yourlinks how is it that when deployed it is now got an extra piece to the addressing ? JMG --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
