Thanks for your help! I think a better solution would be to add this
snippet into newapp/WEB-INF/web.xml:
<servlet-mapping>
<servlet-name>newapp</servlet-name>
<url-pattern>/servlet/newapp/*</url-pattern>
</servlet-mapping>
So, you don't need to enable the invoker servlet (there were security
issue(s) with it at some point in time).
Now onto figuring out why "newapp" causes log4j problems for the stock
example tomcat 5.0.16 webapps!
Regards,
Daniel
On Mon, 15 Dec 2003, Akmal Sarhan wrote:
> for version 5.0.* of tomcat you will have to uncomment the following two
> snippets in $tomcat/conf/web.xml
>
> <!--
> <servlet>
> <servlet-name>invoker</servlet-name>
> <servlet-class>
> org.apache.catalina.servlets.InvokerServlet
> </servlet-class>
> <init-param>
> <param-name>debug</param-name>
> <param-value>0</param-value>
> </init-param>
> <load-on-startup>2</load-on-startup>
> </servlet>
> -->
>
> <!-- The mapping for the invoker servlet -->
> <!--
> <servlet-mapping>
> <servlet-name>invoker</servlet-name>
> <url-pattern>/servlet/*</url-pattern>
> </servlet-mapping>
> -->
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
