I'm not (yet) an expert in OSGi, I'm just trying to get the wheels spinning.. :)
These legacy bits are a bit trickier:
./jena-core/src/main/java/com/hp/hpl/jena/rdf/model/impl/RDFReaderFImpl.java:
return (RDFReader) Class.forName(className)
./jena-core/src/main/java/com/hp/hpl/jena/rdf/model/impl/RDFWriterFImpl.java:
return (RDFWriter) Class.forName(className).newInstance();
./jena-core/src/main/java/com/hp/hpl/jena/ontology/impl/OntModelImpl.java:
owlSyntaxCheckerClass =
Class.forName(owlSyntaxCheckerClassName);
.. specially as jena-arq RIOT registers its replacement readers and
writers by classname.
That is what IMHO is preventing each jena-* submodule to be
independent OSGi bundles.
It should be possible to fix these by passing in the actual Class
instead (with a deprecated method for the String className).
But the jena-osgi solution should in theory work well, by basically
shadowing in jena-arq, jena-core, jena-tdb and jena-iri to the same
bundle.
I'll have another go to update my pull request - sorry for letting
this slip earlier. Now that we use the bundle version of jsonld-java
(0.5.1) it looks a bit cleaner as well.
On 7 January 2015 at 11:10, Andy Seaborne <a...@apache.org> wrote:
> Where are we on this item?
>
> Must be time soon for the next Jena release and getting this in as an
> addition binary artifact would be excellent. As ever, getting feedback
> before releases is slow so a way forward is to include a new binary
> artifact, expecting to iterate it a bit.
>
> A quick look for Class.forName, many are irrelevant (SDB, Fuseki1, testing).
>
> I don't use OSGi so I'm looking/hoping/needing an expert who will sprinkle
> the techno-fairy dust.
>
> Andy
--
Stian Soiland-Reyes
Apache Taverna (incubating)
http://orcid.org/0000-0001-9842-9718
