Hi Daniel,
I tried this under Tomcat 4.1.? and it didn't work when you
went to http://localhost:8080/newapp/servlet/newapp (no trailing /).
I guess Tomcat is picky about this. As I stated in a previous post,
adding:
<servlet-mapping>
<servlet-name>newapp</servlet-name>
<url-pattern>/servlet/newapp</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>newapp</servlet-name>
<url-pattern>/servlet/newapp/*</url-pattern>
</servlet-mapping>
to newapp/WEB-INF/web.xml maps both urls properly.
David
-----Original Message-----
From: Daniel [mailto:[EMAIL PROTECTED]
Sent: December 15, 2003 9:31 AM
To: Turbine Users List
Subject: Re: feedback for tdk 2.3 (dated 2003-12-10)
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]