Hi All,
I have problems running derby with network connector in an OSGi environment.
I created my own bundle for the starter and use an Activator to start
derby (see below).
I have also attached to Manifest of my bundle. Probably there are more
imports missing but this is as far as I got.
Hi Christian,
I did succeed on deploying a network server bundle on OSGi.
To build it I did the following things,
In the maven I just include
dependency
groupIdorg.apache.derby/groupId
artifactIdderby/artifactId
version${derby.version}/version
Hi Loic,
Thanks for the fast reply. I have also seen that there are split
packages and think this is a problem.
I hope the derby team can fix that in one of the next releases.
Do you package the derby jars inside your own jar? I would like to have
a solution that works with the derby jars as
Hi again,
Yes I embed all the content of both jars inside the bundle (you can notice I
did not put scopeprovided/scope on dependancies). I tried to do other
stuff with separate (bundlelized) jars. But it is impossible with this split
package, because your application bundle will try to bind to
Hi All,
I have problems running derby with network connector in an OSGi environment.
I created my own bundle for the starter and use an Activator to start
derby (see below).
I have also attached to Manifest of my bundle. Probably there are more
imports missing but this is as far as I got.
