maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benson Margulies <>
Subject Re: Need a small sax parser for m-s-u
Date Sun, 13 Jan 2013 19:39:11 GMT
Well, you could scan for the JRE's builtin SPI file and pass the class
name you acquire to

It is rather annoying that these classes don't let you say 'give me
the stock JRE method, ignore the system property'.

Or you could write down a list consisting of the class name used in
the Oracle JRE and the class name used in the IBM JDK, and try them in

On Sun, Jan 13, 2013 at 2:09 PM, Kristian Rosenvold
<> wrote:
> We switched to SAX parsing in m-s-u, and we just had an interesting
> issue (
> which basically happens because some plugin sets org.xml.sax.driver to
> point to a variable that is only present in that plugins classloader,
> when m-s-u later tries to instantiate a sax parser it blows up.
> This happens because the standard instantiation algorithm in
> org.xml.sax.helpers.XMLReaderFactory.createXMLReader() is
> not good enough for us. To my knowledge there is no standard way to
> determine what implementation is in use for different JDK's,
> so the best option is probably to shade in a nice small version of a
> sax parser from somewhere.
> I tried shading in xerces, which works nicely, but is hardly "small".
> Anyone have any other suggestions ?
> Kristian
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message