I have a requirement to inject custom DOCTYPE entity declarations into xincluded documents. Currently I am using an org.xml.sax.EntityResolver to accomplish this. When my EntityResolver[1] understands a request it creates and returns a special InputSource[2]. This however gives me problems with an xinclude that is an xml file but that has specified parse="text". The EntityResolver has no idea about that fact and so it does these injections anyway (these are docbook documentation examples, the end result being that the "injected" doctype ends up in the examples as well).
Searching around led me to find org.apache.xerces.xinclude.XIncludeHandler which *seems* like it would be a better place to tie in this processing. So my first question is whether that is the case; am I barking up the right tree here? Assuming so, I am having difficulty understanding how to tel Xerces to use my XIncludeHander instead of its built-in one. All the examples I have seen use a configuraton to completely set up the pipeline (org.apache.xerces.parsers.XIncludeAwareParserConfiguration). However all the examples I saw do this from the command line by specifying -D to name this configuration. I do not have that option (easily). So is there another way to define the pipeline to use? Ideally, is there a way to just alter one part of the pipeline? I have seen the "http://apache.org/xml/properties/internal/xinclude-handler"; setting, but I have no idea how to leverage it. Thanks. [1] http://github.com/sebersole/jdocbook-core/blob/master/src/main/java/org/jboss/jdocbook/xslt/XIncludeEntityResolver.java [2] http://github.com/sebersole/jdocbook-core/blob/master/src/main/java/org/jboss/jdocbook/util/FileUtils.java -- Steve Ebersole <st...@hibernate.org> http://hibernate.org --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
