I discovered what has changed is that later versions of Tomcat (ie 3.3x and 
4.0x) are much more picky about the order of things in the web.xml file. I 
reordered things in mine and things worked much better ;-)

  At 12:56 PM 5/30/2002 -0400, you wrote:
>The contents of the web.xml is defined by the Servlet 2.2
>spec, which hasn't changed.  More detail will be needed
>to tell what is going wrong.  You can set the debug level
>on SimpleMapper1 in server.xml to get more clues about
>why your servlet isn't being found.
>
>Cheers,
>Larry
>
> > -----Original Message-----
> > From: Maureen Barger [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 30, 2002 11:22 AM
> > To: [EMAIL PROTECTED]
> > Subject: moving from 3.2 to 3.31
> >
> >
> > Hi -- I am having some trouble moving an application from
> > tomcat 3.2 to 3.31.
> > In my server.xml, I have pointed the ContextXmlReader to look
> > at my custom
> > apps.xml. My context is mounts and I can access it. But in
> > the web.xml of
> > the application I have defined a servlet to map to a location
> > and it is not
> > loading -- I get a 404.
> > i.e. <servlet>
> >       <servlet-name>brand</servlet-name>
> >       <servlet-class>JarBranderServlet</servlet-class>
> > </servlet>
> >
> >    <servlet-mapping>
> >       <servlet-name>brand</servlet-name>
> >       <url-pattern>/brand</url-pattern>
> >       </servlet-mapping>
> >       <servlet-mapping>
> >       <servlet-name>brand</servlet-name>
> >       <url-pattern>/brand/*</url-pattern>
> >    </servlet-mapping>
> >
> > Has defining servlets changed in 3.31 as well? (So much else
> > has!) The only
> > clue in the docs is the application deployment doc, which
> > warns that it is
> > outdated.

========================================================
Maureen Barger, CIT/ID, Cornell University
Ithaca, NY 14850
[EMAIL PROTECTED]
http://mo.cit.cornell.edu/

Nature goes her own way and all that to us seems an exception
is really according to order.
--Johann Wolfgang von Goethe


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to