Note that, so many contributors here mention, the servlet invoker is turned
off for security reasons. You can reinstate it, but it is considered better
to map your servlet in the application's web.xml file.
Regards,
Wilson
-
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
-
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. [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
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
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
New info: I don't have a web.xml for this context. In Tomcat 4.0.5 it was
not a problem. Is this something they changed for 4.1.18 that you must have
one defined? If so, what would be the minimal web.xml that I could get by
with? Thanks,
Kenny
- Original Message -
From: Kenny G.
. [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 07, 2003 9:47 AM
To: Tomcat Users List
Subject: Re: Status 404 - resource not available
New info: I don't have a web.xml for this context. In
Tomcat 4.0.5 it was
not a problem. Is this something they changed for 4.1.18
that you must