Hello Dave, one question, do you use Olingo V2 or V4 or both?
For Olingo V4 there exists currently no way to change the used XMLInputFactory
in the „ODataXmlDeserializer"
private static final XMLInputFactory FACTORY = new InputFactoryImpl();
For Olingo V2 you can set the „System Property“ to change the used
„XMLInputFactory/XMLOutputFactory“.
See example below for Woodstox/Default JDK6.
Woodstox:
System.setProperty("javax.xml.stream.XMLInputFactory",
"com.ctc.wstx.stax.WstxInputFactory");
System.setProperty("javax.xml.stream.XMLOutputFactory",
"com.ctc.wstx.stax.WstxOutputFactory");
Default JDK6:
System.setProperty("javax.xml.stream.XMLInputFactory",
"com.sun.xml.internal.stream.XMLInputFactoryImpl");
System.setProperty("javax.xml.stream.XMLOutputFactory",
"com.sun.xml.internal.stream.XMLOutputFactoryImpl");
Best Regards,
Michael
> Am 09.10.2015 um 15:29 schrieb Vilaverde, David <dvilave...@informatica.com>:
>
> Hi,
>
> I currently have a product in which I am using Metro and OLingo. The Metro
> stack depends on wstx-asl and olingo on aalto-xml and I'm running into issues
> where the XMLInputFactory finds aalto-xml over wstx-asl which is causing
> other serialization issues for Metro. I tried removing aalto-xml from the
> classpath but then I have issues with OData V4 XML because of a
> NoClassDefFound exception when initializing ODataXmlDeserializer. I noticed
> the org.apache.olingo.odata2.core.commons.XmlHelper doesn't directly import
> aalto but instead uses XMLInputFactory.newInstance(), so the question is can
> all other usages of aalto be replaced with XMLInputFactory or
> XMLOutputFactory, etc?
>
> If so, I would gladly open a Jira issue and contribute a patch back to the
> OLingo project via github.
>
> Dave
>
signature.asc
Description: Message signed with OpenPGP using GPGMail
