Re: WEB.XML changes and init parm settings in WebSphere

Paul,

I don't know if WebSphere is special but I doubt restarting the
application can truly reclaim all resources so I would use a complete
restart given the opportunity. I would avoid defining setup parameters
in the web.xml and use a configuration file or initialization Servlet
instead. In some cases, like security roles, you are stuck. It wouldn't
be too hard to write an ant script or application that unpacks the war,
prompts for values, updates web.xml, and repacks.

David Morris

>>> pholm@xxxxxxxxxxxxxxxxx 10/30/2004 8:04:13 AM >>>
Two part question:

#1  We have a servlet running in WebSphere Express 5.1 on the iSeries
with
init parms in web.xml.  Changes to web.xml in the ....installedApps/
directory don't seem to take effect even when RESTARTING the
application or
even the application server that the web app is in.

When is web.xml read by WAS express and what is the recommended method
forcing a "restart" and therefore a reread of web.xml?

#2  Related, when delivering a .war file with a web.xml file in it
that
needs to be customized by end users prior to installation into
WebSphere,
what is the easiest way to accomplish this?  We are currently having
them
unzip the .war, make the changes to web.xml and rezip but there has to
be a
better way I'm hoping.

Thanks,  Paul Holm

Business: 760-432-0600   Home: 760-432-6550
Cell:  760-415-8830
PlanetJ - Makers of WOW  (AKA... WebSphere on Steroids)