Hello Andy,
> The error in tests 2 and 3 looks like it is because Jena initialization
> has not happened.
> The default is to use ServiceLoader which looks for META-INF/services/
> org.apache.jena.system.JenaSubsystemLifecycle
Apparently there was an effort to fix this in the combined Jena-OSGI bundle
which META-INF/services/org.apache.jena.system.JenaSubsystemLifecycle
configuration already lists the main subsystems in the appropriate order:
org.apache.jena.system.InitJenaCore
org.apache.jena.riot.system.InitRIOT
org.apache.jena.sparql.system.InitARQ
org.apache.jena.tdb.sys.InitTDB
I am wondering whether and how Jena v3 is used in OSGi environments so far?
> Or you can inject a different procedure with JenaSystem.setSubsystemRegistry
This seems the only option to explicitly debug and configure the
initialization in an OSGi runtime.
Thanks for the reference!
Jaro
--
Jaroslav Pullmann
Fraunhofer Institute for Applied Information Technology FIT
Web Compliance Center: http://imergo.com/ · http://imergo.de/
Schloss Birlinghoven, D-53757 Sankt Augustin, Germany
Phone: +49-2241-142623 · Fax: +49-2241-142065
