Gregory Murphy wrote:
I wonder if a more portable approach to the same problem would be to allow
applications that call transformers to specify URL resolvers
I don't think this link could be any more appropriate:
http://access1.sun.com/technotes/00762.html
And non-JAXP XSLT processors sometimes have their own way of supplying
external URI resolvers. It's a common requirement. In 4Suite, which is Python
based, we've added it as an optional constructor in an InputSource.
Mike
--
Mike J. Brown | http://skew.org/~mike/resume/
Denver, CO, USA | http://skew.org/xml/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list