Tobias, > dbXML sends a startdocument() and a stopdocument() althought the XSP has > done this already. I pached the code so the dbXML doen't anymore. Until now > no side effect are detected (The db server runs with the old (unpached) > *.jar).
nice to know that you solved the problem. I might suggest you, though, what I think is a better solution: instead of patching dbXML you may just use a consumer that ignores the start and endDocument events. There is an utility class which does exactly so, look in org.apache.cocoon.xml.IncludeXMLConsumer, which takes an XMLConsumer as a parameter in the constructor to forward events to. Basically this should be enough for you: document.getContentAsSAX(new IncludeXMLConsumer(xmlConsumer)); Let me know if you are willing to try it and if it works: this would save you from having to continuously patch dbXML whenever a new version comes out. Ciao, -- Gianugo --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>