this is mentioned in the 5.5 release notes. check out the readme file.
now, it does tell you how to get your /servlets/ path back, but it also says
that it's not supported in production. not sure what that means. try
accessing your servlets without the /servlets/ in your path and see what
happens.
> Hello group,
>
[quoted text clipped - 9 lines]
> Many thanks,
> Magnus
Chris Smith - 18 Jun 2006 07:04 GMT
> now, it does tell you how to get your /servlets/ path back, but it also says
> that it's not supported in production. not sure what that means.
They are basically trying to get across the concept that it's a really,
really bad idea to do things that way. We've had the web.xml file for
quite a few years now, and it's time to move on. Explicit servlet
mappings lead to better security situations, cleaner and less complex
applications, and more flexibility. It escapes me why anyone would want
a /servlets directory.

Signature
Chris Smith - Lead Software Developer / Technical Trainer
MindIQ Corporation
> Hello group,
>
[quoted text clipped - 9 lines]
> Many thanks,
> Magnus
That url is using the dreaded "invoker" servlet, source of any number
of hard to figure out bugs - see
http://faq.javaranch.com/view?InvokerServlet
Just bite the bullet and learn to use web.xml - you will be glad you did.
Bill