You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xerces.apache.org by Olivier Rossel <ol...@gmail.com> on 2009/10/14 18:13:54 UTC
XSLT and then XInclude.
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-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: XSLT and then XInclude.
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Olivier,
Currently XInclude is only supported as part of the parsing process. The
best you can do today with Xerces is to serialize the document (you could
write to memory instead of a file) and then process it with an XInclude
aware SAX or DOM parser.
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Olivier Rossel <ol...@gmail.com> wrote on 10/14/2009 12:13:54 PM:
> 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-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org