Apparently you will have to use the /servlet in the URI if you do not specify a
servlet mapping for your servlet in the web.xml file. I have provided an illustration
below:
<web-app>
...
<servlet>
<servlet-name>MyServlet</servlet-name>
<servlet-class>com.mywebsite.package.MyServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>MyServlet</servlet-name>
<url-mapping></url-mapping>
</servlet-mapping>
...
</web-app>
Thanks,
Paul Idusogie
Technical Architect
Consulting Services
Stellent Inc.
7777 Golden Triangle Drive
Eden Prairie, MN 55104
Desk: 952.656.2755
Fax: 952.903.2115
Email: [EMAIL PROTECTED]
website: http://www.stellent.com
-----Original Message-----
From: Dave J Dandeneau [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 11, 2002 4:33 PM
To: Struts Users Mailing List
Subject: /servlet is the industry standard?
Our current client is inquiring why we are not using /servlet as the prefix to our
URIs. They are saying that /servlet is the industry standard. I have argued that a
struts application only has one servlet (possibly two if you include the validator)
and therefore it wouldn't make any sense to do it that way in a struts application.
Is this truly an industry standard? Would there be any reasoning to try to mimic this?
Can this even be done if you have multiple web-apps?
Wouldn't it look more like <domain>/<contextpath>/servlet and not <domain>/servlet?
Any feedback would be greatly appreciated.
Thanks,
dave dandeneau
