Hey Mike

Maybe the context is marked reloadable="false" in the server.xml file.

Here is an example of a line in one my server.xml files:

<Context path="/beesharp" reloadable="false"
docBase="c:\home\eclipseworkspace\beesharp"
workDir="c:\home\eclipseworkspace\beesharp\work\org\apache\jsp"/>

Here is a link to the Tomcat docs. They should be similar to WAS.

http://tomcat.apache.org/tomcat-5.0-doc/config/context.html

Thanx, PLA


On 1/25/07, Mike Burdette <Mike.Burdette@xxxxxxxxxxxxx> wrote:

Hi all:

We have a web app deployed in WAS 5.1. I need to add a servlet to the app.
(This is a web facing application.) Instead of rebuilding the war file, I
just placed the servlet class file in the WEB-INF/classes/<package name>
folder and modified the web.xml to add the <servlet> and <servlet-mapping>
information. However, the app never seems to recognize this new servlet.
We get a 404 page when it is called and there is no mention of it at all
in the SystemOut.log. I have even taken the web.xml from another system
with the same web app and replaced the old web.xml with it. The webfaced
app runs fine, but my new servlet is still not being found. I can tell
this by going in to the Admin Console and looking at the deployment
descriptor The servlet is not shown.

Any ideas what may be going on?

thanks in advance,

Mike
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].