Yeah.  It surprises me that you say that, since I believe web.xml files
are required for a context to start up.  I'd definitely read the Servlet
spec if you haven't already.

-- 
Tim Moore / Blackboard Inc. / Software Engineer
1899 L Street, NW / 5th Floor / Washington, DC 20036
Phone 202-463-4860 ext. 258 / Fax 202-463-4863


> -----Original Message-----
> From: Kenny G. Dubuisson, Jr. [mailto:[EMAIL PROTECTED]] 
> Sent: Monday, February 10, 2003 1:42 PM
> To: Tomcat Users List
> Subject: Re: Status 404 - resource not available
> 
> 
> I don't have a web.xml defined.  In my old Tomcat 4.0.5 I 
> didn't need one; do I need one now?  Thanks, Kenny
> 
> ----- Original Message -----
> From: "Tim Moore" <[EMAIL PROTECTED]>
> To: "Tomcat Users List" <[EMAIL PROTECTED]>
> Sent: Monday, February 10, 2003 12:37 PM
> Subject: RE: Status 404 - resource not available
> 
> 
> > Check your web.xml. Servlets and serlet mappings must be 
> declared in 
> > web.xml.  Check the servlet spec for details.
> >
> > --
> > Tim Moore / Blackboard Inc. / Software Engineer
> > 1899 L Street, NW / 5th Floor / Washington, DC 20036
> > Phone 202-463-4860 ext. 258 / Fax 202-463-4863
> >
> >
> > > -----Original Message-----
> > > From: Kenny G. Dubuisson, Jr. [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, February 10, 2003 1:26 PM
> > > To: Tomcat Users List
> > > Subject: Re: Status 404 - resource not available
> > >
> > >
> > > Sorry for the re-post but I didn't get any responses and 
> I'm really 
> > > stuck on this.  Thanks, Kenny
> > >
> > > ----- Original Message -----
> > > From: "Kenny G. Dubuisson, Jr." <[EMAIL PROTECTED]>
> > > To: "Tomcat Users List" <[EMAIL PROTECTED]>
> > > Sent: Friday, February 07, 2003 9:29 AM
> > > Subject: Status 404 - resource not available
> > >
> > >
> > > > I just reloaded my development box and I can't get my 
> servlet to 
> > > > be recognized; I get a Status 404 error - resource not 
> available.  
> > > > I'm not
> > > sure
> > > > where to start diagnosing the problem.  My context (named 
> > > > "kcmria") works...ie if I put in 
> http://192.168.1.61/kcmria I get 
> > > > the
> > > directory
> > > > listing of $CATALINA_HOME/webapps/kcmria which is what I
> > > would expect.
> > > But
> > > > I can't get anything in
> > > $CATALINA_HOME/webapps/kcmria/WEB-INF/classes
> > > > to
> > > be
> > > > recognized.
> > > >
> > > > I tried copying HelloWorldExample over to my servlet 
> directory but 
> > > > can't
> > > see
> > > > it either.  I think it must be something with my 
> context.  Here is 
> > > > what
> > > I've
> > > > defined in server.xml:
> > > >
> > > > <Context path="/kcmria" docBase="kcmria" debug="0"
> > > reloadable="true"
> > > > crossContext="true">
> > > >     <Logger className="org.apache.catalina.logger.FileLogger"
> > > > prefix="localhost_kcmria_log."
> > > >          suffix=".txt" timestamp="true" />
> > > > </Context>
> > > >
> > > > My mod_jk.conf looks like this:
> > > >
> > > > JkMount /kcmria ajp13
> > > > JkMount /kcmria/* ajp13
> > > >
> > > > Any ideas where I should start looking?  Thanks,
> > > > Kenny
> > > >
> > > >
> > > >
> > > 
> --------------------------------------------------------------------
> > > -
> > > > To unsubscribe, e-mail: 
> [EMAIL PROTECTED]
> > > > For additional commands, e-mail: 
> > > > [EMAIL PROTECTED]
> > > >
> > >
> > >
> > > 
> --------------------------------------------------------------------
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: 
> [EMAIL PROTECTED]
> > >
> > >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

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

Reply via email to