Yes, be really careful with shading and similar XML stuff, the IBM JRE has a lot of XML processing in it built in, and it can clash.
-Chris On Mon, Jan 14, 2013 at 6:39 AM, Benson Margulies <bimargul...@gmail.com>wrote: > Well, you could scan for the JRE's builtin SPI file and pass the class > name you acquire to > > http://docs.oracle.com/javase/6/docs/api/org/xml/sax/helpers/XMLReaderFactory.html > . > > 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 > order. > > > On Sun, Jan 13, 2013 at 2:09 PM, Kristian Rosenvold > <kristian.rosenv...@gmail.com> wrote: > > We switched to SAX parsing in m-s-u, and we just had an interesting > > issue (https://jira.codehaus.org/browse/SUREFIRE-950) > > 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: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
