Hi, There’s an OSGi spec all about parsing XML. You can read it at https://osgi.org/specification/osgi.cmpn/7.0.0/util.xml.html <https://osgi.org/specification/osgi.cmpn/7.0.0/util.xml.html>. In summary, you want to be injected with a SAXParserFactory service and use that.
Best Regards, Tim > On 17 Sep 2018, at 13:04, Markus Rathgeb <maggu2...@gmail.com> wrote: > > I have found also this one: > http://apache-sling.73963.n3.nabble.com/jaxb-OSGI-amp-com-sun-xml-bind-Cannot-be-resolved-and-overwritten-by-Boot-Delegation-td4046690.html > > <http://apache-sling.73963.n3.nabble.com/jaxb-OSGI-amp-com-sun-xml-bind-Cannot-be-resolved-and-overwritten-by-Boot-Delegation-td4046690.html> > > As I am using a SAX parser I don't think I will run into some > "OSGi-compatible concerning class loading" problems.. > But WDYT, does it make more sense to rely on a working > "SAXParserFactory.newInstance()"?
