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.
Metadata creates a logger and ModelCom, RDFReaderFimpl, JenaRuntime
don't appear to so if this is the first call into Jena, log4j
initialization occurs.
Have you been using only released versions, no snapshots? The
log4j.properties was taken out between last non-Apache release and first
Apache release.
As a library, this is a bit of a no-win situation but if we can force
all first-use code through a place where we can fix log4j if there is no
system property "log4j.configuration".
Andy
