And if all those reasons weren't enough, it's also depricated and not
portable. Changing servlet engines or upgrading may break your webapp.
Better to do it right from the beginning than have to recode later.
--David
David Delbecq wrote:
- Because it way unsecure. It can invoke pretty any
- Because it way unsecure. It can invoke pretty any class in your webapp
class path. This include legacy servlet (like com.company.TheServlet)
but also your test servlet, the servlets you developped for quick admin
hacks locally and you didn't remove from code.
- Invoker servelt is one unique serv
ok i found some expamples
but why not the invoker servlet
it seems to be just the right one
>I think you are looking for the Invoker servlet. That's not
>recommended. See the servletexamples webapp's web.xml file for a
>standards compliant way to map servlet to request uri's
>
>--David
>
>
Hmmm
could you give me a link please
have not found a good example
>I think you are looking for the Invoker servlet. That's not
>recommended. See the servletexamples webapp's web.xml file for a
>standards compliant way to map servlet to request uri's
>
>--David
>
>[EMAIL PROTECTED] wrote:
I think you are looking for the Invoker servlet. That's not
recommended. See the servletexamples webapp's web.xml file for a
standards compliant way to map servlet to request uri's
--David
[EMAIL PROTECTED] wrote:
Hi
in normal case you call servelts as followed
/servlet/packetName for exa
Hi
in normal case you call servelts as followed
/servlet/packetName for example servlet/xinfo/test/Testservlet
how can I reach this
thanks for help
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail
