I appreciate very much the XInclude features of Xerces. But unfortunately my documents have a tricky proprietary include mechanism. I have a XSLT that can resolve them into perfectly legal xi:include tags.
I wish I could create the following pipeline: - my original document is transformed by a XSLT processor - the transformed document is sent as SAX or DOM to Xerces, - Xerces manages the XInclude inclusion and creates a new DOM Document, where external contents have been inlined. Does it sound possible? The alternatives are 1: to save the result of the XSLT in a file, and then parse than file with Xerces 2: manage the XInclude from inside the XSLT, but both sound infinitely less convinient. --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
