I am rather confused here.
application.xml
<application>
<display-name>Abc</display-name>
<description>abc</description>
<module>
<web>
<web-uri>warapp</web-uri>
<context-root>jv1</context-root>
</web>
</module>
</application>
allows only one context root.
web.xml
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
.........
</servlet>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
gives nothing.
I do not see how I can set multiple URLs for the same Struts app.
Craig McClanahan <[EMAIL PROTECTED]>
11/11/2004 09:33 AM
Please respond to
"Struts Users Mailing List" <[EMAIL PROTECTED]>
To
Struts Users Mailing List <[EMAIL PROTECTED]>
cc
Subject
Re: Struts app to be passed a parameter (of some kind)
On Thu, 11 Nov 2004 08:14:12 -0500, John Vincent
<[EMAIL PROTECTED]> wrote:
> Need one Struts app, but must have multiple URLs.
>
> Thus
> http://www.jv.com/company1
> http://www.jv.com/company2
Why not just configure your servlet container to treat both context
paths as the same app? For example, in Tomcat, you can create two
<Context> elements with different paths but the same document base
directory.
>
> actually start the same Struts app, say
>
> http://www.jv.com/myApp
>
> but must "pass" something into the Struts app so that it knows who, or
> rather, which URL invoked it.
>
The request.getContextPath() method would tell your application which
way it was invoked.
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
NOTICE: This communication may contain confidential, proprietary or
legally privileged information. It is intended only for the person(s) to
whom it is addressed. If you are not an intended recipient, you may not
use, read, retransmit, disseminate or take any action in reliance upon it.
Please notify the sender that you have received it in error and
immediately delete the entire communication, including any attachments.
Towers Perrin does not encrypt and cannot ensure the confidentiality or
integrity of external e-mail communications and, therefore, cannot be
responsible for any unauthorized access, disclosure, use or tampering that
may occur during transmission. This communication is not intended to
create or modify any obligation, contract or warranty of Towers Perrin,
unless the firm clearly expresses such an intent.
