RE: When the Struts webapp is not at the root of the server

2003-07-23 Thread Doyle, Michael J
I declare the app in the weblogic.properties file, thusly:


weblogic.httpd.webApp.myStrutsApp=/home/weblogicInstances/Wls_port/myStrutsA
pp

The web.xml file in myStrutsApp/WEB-INF contains a bunch of weblogic
specific s, the Struts action servlet config:

 
 action 

org.apache.struts.action.ActionServlet 
 
  config 
  /WEB-INF/struts-config.xml 
 
 1 
 

... The action servlet mapping:

 
  action 
  *.do 
  

... And some taglib declarations

Is there some way to parameterize the servlet or the struts-config.xml to
get the behaviour I want? I suspect there is not, having looked at the code
of RequestUtils. But hopefully someone else out there has dealt with this?

Thanks,
- Mike

-Original Message-
From: Adam Levine [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 23, 2003 12:35 PM
To: [EMAIL PROTECTED]
Subject: RE: When the Struts webapp is not at the root of the server


How did you declare the app context?  (in the web.xml, I believe)


From: "Doyle, Michael J" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: When the Struts webapp is not at the root of the server
Date: Wed, 23 Jul 2003 12:29:25 -0400

Still haven't found a solution for this. Any suggestions?

Thanks,
- Mike

 >  -Original Message-
 > From:Doyle, Michael J
 > Sent:Wednesday, July 09, 2003 9:43 AM
 > To:  '[EMAIL PROTECTED]'
 > Subject: When the Struts webapp is not at the root of the server
 >
 > Hi,
 >
 > I have been working on a Struts based web application. Things have been
> going fine developing on http://localhost:7001/myStrutsApp  >
<http://localhost:7001/myStrutsApp> . I've discovered a problem when I  >
deploy to http://www.somehost.com/somepath/myStrutsApp
 > <http://www.somehost.com/somepath/myStrutsApp> .
 >
 > Struts gets confused with the paths it generates to Actions and rewritten
> URLs. It seems that Struts assumes the web application is always at the  >
root of the server, e.g. http://www.somehost.com/myStrutsApp
 > <http://www.somehost.com/myStrutsApp> .
 >
 > It produces
 >  
 >
 > when what I need is
 >  
 >
 > Thus, the   and any other tag that rewrites the URL
> don't work properly in this configuration.  >  > Is there a workaround for
this? Perhaps something to do with module  > configuration? The web server
is Netscape 3.5.1 and the app server is  > Weblogic 5.10 sp13.  >  > Thanks
for any help,  > - Mike  >  >

_
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail


-
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]



RE: When the Struts webapp is not at the root of the server

2003-07-23 Thread Adam Levine
How did you declare the app context?  (in the web.xml, I believe)

From: "Doyle, Michael J" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: When the Struts webapp is not at the root of the server
Date: Wed, 23 Jul 2003 12:29:25 -0400
Still haven't found a solution for this. Any suggestions?

Thanks,
- Mike
>  -Original Message-
> From:  Doyle, Michael J
> Sent:  Wednesday, July 09, 2003 9:43 AM
> To:    '[EMAIL PROTECTED]'
> Subject:   When the Struts webapp is not at the root of the server
>
> Hi,
>
> I have been working on a Struts based web application. Things have been
> going fine developing on http://localhost:7001/myStrutsApp
> <http://localhost:7001/myStrutsApp> . I've discovered a problem when I
> deploy to http://www.somehost.com/somepath/myStrutsApp
> <http://www.somehost.com/somepath/myStrutsApp> .
>
> Struts gets confused with the paths it generates to Actions and rewritten
> URLs. It seems that Struts assumes the web application is always at the
> root of the server, e.g. http://www.somehost.com/myStrutsApp
> <http://www.somehost.com/myStrutsApp> .
>
> It produces
>
>
> when what I need is
>
>
> Thus, the   and any other tag that rewrites the URL
> don't work properly in this configuration.
>
> Is there a workaround for this? Perhaps something to do with module
> configuration? The web server is Netscape 3.5.1 and the app server is
> Weblogic 5.10 sp13.
>
> Thanks for any help,
> - Mike
>
>
_
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: When the Struts webapp is not at the root of the server

2003-07-23 Thread Doyle, Michael J
Still haven't found a solution for this. Any suggestions?

Thanks,
- Mike

>  -Original Message-
> From: Doyle, Michael J  
> Sent: Wednesday, July 09, 2003 9:43 AM
> To:   '[EMAIL PROTECTED]'
> Subject:      When the Struts webapp is not at the root of the server
> 
> Hi,
> 
> I have been working on a Struts based web application. Things have been
> going fine developing on http://localhost:7001/myStrutsApp
> <http://localhost:7001/myStrutsApp> . I've discovered a problem when I
> deploy to http://www.somehost.com/somepath/myStrutsApp
> <http://www.somehost.com/somepath/myStrutsApp> . 
> 
> Struts gets confused with the paths it generates to Actions and rewritten
> URLs. It seems that Struts assumes the web application is always at the
> root of the server, e.g. http://www.somehost.com/myStrutsApp
> <http://www.somehost.com/myStrutsApp> . 
> 
> It produces 
>   
> 
> when what I need is 
>   
> 
> Thus, the   and any other tag that rewrites the URL
> don't work properly in this configuration.
> 
> Is there a workaround for this? Perhaps something to do with module
> configuration? The web server is Netscape 3.5.1 and the app server is
> Weblogic 5.10 sp13.
> 
> Thanks for any help,
> - Mike
> 
> 


RE: When the Struts webapp is not at the root of the server

2003-07-09 Thread Doyle, Michael J
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 /somepath to the root path of my app
server. Thus, the actual path to my resources is
/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 /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]



Re: When the Struts webapp is not at the root of the server

2003-07-09 Thread Jamie M. Guillemette
Hi Mike,

Your webapp would be built as if it was running from /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]



When the Struts webapp is not at the root of the server

2003-07-09 Thread Doyle, Michael J
Hi,

I have been working on a Struts based web application. Things have been
going fine developing on http://localhost:7001/myStrutsApp
 . I've discovered a problem when I
deploy to http://www.somehost.com/somepath/myStrutsApp
 . 

Struts gets confused with the paths it generates to Actions and rewritten
URLs. It seems that Struts assumes the web application is always at the root
of the server, e.g. http://www.somehost.com/myStrutsApp
 . 

It produces 


when what I need is 


Thus, the   and any other tag that rewrites the URL
don't work properly in this configuration.

Is there a workaround for this? Perhaps something to do with module
configuration? The web server is Netscape 3.5.1 and the app server is
Weblogic 5.10 sp13.

Thanks for any help,
- Mike