I will bootstrap the new configuration code by writing a DOM based JNDI directory context to provide some compatibility with the current server.xml.
I'll start experimenting with the JNDI naming conventions we'll be using as I implement the context (obviously, that will happen in the test program I'll write). I'd like to advocate mirroring all changes to the configuration to the backend immediately (without the need for a commit as it is done now). The initial experimental implementation will use: - a DOM tree to mirror the XML, and that easily maps to the structure - algorithms wise, it is likely to look like the WARDirContext - I may use JDOM, as some DOM to XML serialization is needed, and isn't provided by JAXP Note: The only reason why I want to use something like JDOM is for the serialization. If someone has ideas about how to do it without JDOM (I'm fine with using straight DOM), let me know (I'd like to avoid writing my own serialization code if possible, although it could be useful to do so for performance reasons). Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
