On 8/12/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > Which still doesn't help with reloading web.xml. :)
It's conceivable that a servlet container could provide such a feature, but I don't know of any that do so. There will also be limits in how much flexibility such a feature really buys you, in a couple of dimensions: * If your application only reads an init parameter at startup time, it would have to have its logic modified in order to check for changes later. * There are no events in the servlet API to notify you when such a change was made, so you'll have to poll for it. * Reloading web.xml without rebuilding the application class loader means you can't really recompile an individual class and change its behavior (which seems like a common desire, especially during development). You're likely to need to reload the app anyway. If I had configuration settings that I wanted to make changeable, I'd set them up as application scope attributes, not web.xml settings. > > -- > Wendy Smoak > Craig
