> The DefaultContext is not editable and resources configured for the > DefaultContext are not maintained by the admin application when it > writes out the new server.xml. Instead the resources are merged into > the individual Contexts. Will support for the DefaultContext be added?
Yes good point. I'll try to slightly refactor DefaultContext (using NamingResources, which was introduced after) to allow having clean support for DefaultContext (and avoid some annoying replication in server.xml). I'll need to add get/setNamingResource methods to it (I don't think this is a problem). Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
