> In the cases of DOM, JDOM, and DOM4J, the relevant methods all accept
> org.xml.sax.InputSource, so a switch to using an EntityResolver is
> straightforward in each case.  For Electric XML, the InputStream or Reader
> will have to be unbundled from the InputSource, but is a dependency of
> Jaxen on SAX a desirable thing?  EXML doesn't include SAX, but use of
> InputSource would require this.  (I would say that SAX dependency is
> not a bad thing.)

Jaxen is now seamlessly integrated into EXML (starting with version 6.0),
so any dependency we add will directly affect TME's product, and that 
isn't a good thing to do to a happy customer.  I'll digest your other 
comments, but adding a dependency really isn't an option.

        -bob



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest

Reply via email to