On 11/02/12 20:14, Andy Seaborne wrote:
On 11/02/12 19:09, Dave Reynolds wrote:
Has anything changed in the area of JenaRuntime initialization since the
transition into Apache?
I'm trying to get an OSGi version of apache-jena working but
configurations that worked with pre-apache jena are failing for me.
As far as I can tell the problem is the static initialization chain
ModelCom -> RDFReaderFimpl > JenaRuntime > Metadata
It think (but am far from certain) that properties.loadFromXML is
failing but there's no error, the jena-properties.xml is in the bundle
and the resource stream is opened OK.
So as a hint to help with debugging, are there any recent changes in
this area that are worth knowing about?
Dave
Wild guess : no log4j.properties.
Good thought, thanks, but sadly not that easy.
It seems to be a problem with the change of Xerces versions. Adding
debug-by-print-statement I can see that the
properties.loadFromXML( in );
call is failing thanks to:
Thrown java.lang.ClassCastException:
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
cannot be cast to javax.xml.parsers.DocumentBuilderFactory
which suggests there's an incompatibility between xercesImpl and
xml-apis. Yet the only version of these I'm aware of including are in
the jena-osgi bundle created via Maven and the Maven dependency
resolution trace *looks" right.
Dave
