|
FWIW, I am NOT a WAS expert by any means -- so please take this with a teaspoon of salt ;-) I seem to recall that WAS 5.x will create two copies of the web.xml when it deploys an app. One gets used and the other just sits there. I will guess that you modified "the other one". Personally my preference would be to update the project in WDSC and re-deploy it so that you know it is correct and that the updates in the deployed project won't be lost if it has to be re-deployed at another time. Mike Mike Hockings, P.Eng. WebSphere Development Tools for AS/400 - CODE/Designer & WebFacing ! IBM Canada Ltd. Laboratory hockings@xxxxxxxxxx Mike Burdette <Mike.Burdette@xxxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 01/25/2007 10:51 AM Please respond to Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> To WDSCI-L@xxxxxxxxxxxx, WEB400@xxxxxxxxxxxx cc Subject [WDSCI-L] Updating web.xml not being recognized... 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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.