Let me float the problem by you. Maybe I am overlooking something in the config. We have a hard coded URI that goes "/servlet/com.bo.hsal.HSALServlet?foo" (it is in 3rd party software that we do not have the source for). With the invoker taken out, any call to /servlet fails because it cannot find a context (with the invoker in the config, it finds it in the "default context").
What combination of <servlet> and <servlet-mapping> would you use in the web.xml?
In the web.xml of the app:
<servlet>
<servlet-name>hsalServlet</servlet-name>
<display-name>Stubborn</display-name>
<servlet-class>com.bo.hsal.HSALServlet</servlet-class>
</servlet> <servlet-mapping>
<servlet-name>hsalServlet</servlet-name>
<url-pattern>/hsalServlet</url-pattern>
</servlet-mapping>
http://www.unknown.com/appname/hsalServlet
should respond.
To get
http://www.unknown.com/appname
set
<servlet-mapping>
<servlet-name>hsalServlet</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>To get
http://www.unknown.com
set the app as the default app in the context with the above servlet mapping.
Please note these are my best guess. If I have foo barred somewhere hopefully someone will jump in and correct me.
Doug
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
