Missing OSGI Bundle for rdf2go.impl.jena26-4.7.3.jar

[ruffer]

Hi All,

i am currently testing RDF2Go to use it in my osgi project. I see in
the package structure a package called osgi, which contains a
BundleActivator to register ModelFactory. but the manifest header
contains no osgi entries.The header is just a standard jar manifest
header. Is this known issue? If the is an Activator why dont you
bundlize it. Is the any other way to use it in an OSGI environment ?
Sure, i can bundlize it by my self, i just want to know if i'm doing
some thing wrong.

thanks in advance

ruffer

[Antoni Mylka]

W dniu 2010-10-18 02:00, ruffer pisze:

I haven't heard of anyone trying to use the jena driver in OSGI (or of
anyone trying to actually use the jena driver at all for that matter :).
Still, I'm far from claiming the knowledge of the entire RDF2Go user family.

You're probably not doing anything wrong. The headers aren't generated
and if you whip up a patch that will add those manifest entries,
probably in pom.xml, similar to the way it's done in the sesame module -
Max will gladly accept it.

Max?

Antoni Mylka
antoni...@gmail.com

[Max Voelkel]

i am currently testing RDF2Go to use it in my osgi project. I see in
the package structure a package called osgi, which contains a
BundleActivator to register ModelFactory. but the manifest header
contains no osgi entries.The header is just a standard jar manifest
header. Is this known issue? If the is an Activator why dont you
bundlize it. Is the any other way to use it in an OSGI environment ?
Sure, i can bundlize it by my self, i just want to know if i'm doing
some thing wrong.

thanks in advance

I haven't heard of anyone trying to use the jena driver in OSGI

me neither
 

(or of anyone trying to actually use the jena driver at all for that matter :). Still, I'm far from claiming the knowledge of the entire RDF2Go user family.

You're probably not doing anything wrong. The headers aren't generated and if you whip up a patch that will add those manifest entries, probably in pom.xml, similar to the way it's done in the sesame module - Max will gladly accept it.

Yes, I do accept patches, sure. I am not an OSGi user myself, so I cannot help here personally.

Max

[Gebeyehu Dagne]

Sorry for answering too late and thank you all,

@ Max: I have bundlized the jena driver and it's dependency(RDF2Go Api)
and it works fine for me. I will make some tests and i will send you a
patch.

And i still have a Question,

In RDF2Go i see a project called "rdf2go.layer.autopersist" but i don't
understand the aim of the project. In Jena for example i can do some
thing like this

1. RDF2Go.register(new ModelFactoryImpl() );
2. model = RDF2Go.getModelFactory().createModel();
3. model.setAutocommit(true);
4. model.open();

(line 3) sets the jena model to commit any changes made to the model.
Are you doing something like that in the autopersist module?

Thank you
Gebi

> --
> You received this message because you are subscribed to the Google
> Groups "RDF2Go and RDFReactor (part of semweb4j)" group.
> To post to this group, send email to semw...@googlegroups.com.
> To unsubscribe from this group, send email to semweb4j
> +unsub...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/semweb4j?hl=en.

--
Gebeyehu Dagne <gda...@googlemail.com>

[Max Voelkel]

@ Max: I have bundlized the jena driver and it's dependency(RDF2Go Api)
and it works fine for me. I will make some tests and i will send you a
patch.

Ok, great.
 

And i still have a Question,

In RDF2Go i see a project called "rdf2go.layer.autopersist" but i don't
understand the aim of the project. In Jena for example i can do some
thing like this

    1. RDF2Go.register(new ModelFactoryImpl() );
    2.                 model = RDF2Go.getModelFactory().createModel();
    3.                 model.setAutocommit(true);
    4.                 model.open();

(line 3) sets the jena model to commit any changes made to the model.
Are you doing something like that in the autopersist module?

Yes, I think this was the idea. Honestly, the autopersist project is very very old now and has rarely been used. Maybe we should just delete it. It seems the functionality is already provided both by Jena and by Sesame.

max
 

--
d...@xam.de | http://Xam.de

[Gebeyehu Dagne]

Am Dienstag, den 26.10.2010, 11:25 +0200 schrieb Max Voelkel:
> Yes, I think this was the idea. Honestly, the autopersist project is
> very very old now and has rarely been used. Maybe we should just
> delete it. It seems the functionality is already provided both by Jena
> and by Sesame.

OK, i can say for sure, this funktionality is provided in Jena.I don't
know about Sesame

Thank you a gain for your great work :)

>
>
--
Gebeyehu Dagne <gda...@googlemail.com>