Guys,
At the moment if you create a new XMLResource, there is no way to construct a new DOM tree for it, because calling getContentAsDOM() on a newly created XMLResource throws an exception. You either need to create some initial markup using SAX or XML in a string, then you can get at the resource's Document.
Now, the XMLDB API does not explicitly state what that should happen in this case, but I think it would be reasonable to return an empty DocumentImpl. This can then get populated and be saved back on the document. My tree is patched to do this ATM and seems to be working fine, if there's no objections then I'll commit this patch.
Mike.
-- Mike Gratton <[EMAIL PROTECTED]>, <http://web.vee.net/> "Every motive escalate."
