Scott,

I think there's been a bit of a misunderstanding here - these bundles
do add OSGi metadata to the derbynet bundle so they can be installed
in ServiceMix, but they don't have any provisions to actually
bootstrap or configure the server instance.  We do run Derby
internally when we deploy ODE on ServiceMix 4.3.0, but that's not the
network edition.  However, it would probably not be such a bad idea to
just offer support for Derby in the way you're suggesting.  Like we
could create a bundle which uses the OSGi ConfigAdmin and a Blueprint
file to bootstrap and configure a server or something like that.
Could you raise a JIRA issue for this?  Also, if you fancy taking a
stab at creating this bundle, just let us know and we'll gladly help
you out wherever we can -- we love patches ;)

Regards,

Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



On Tue, Jun 21, 2011 at 5:31 PM, Scott Came <[email protected]> wrote:
> Thanks, JB.  Is there documentation on how the bundle operates?  For example, 
> if I want to change the port that the network server runs on, how would I do 
> that?
>
> Thanks.
> --Scott
>
> -----Original Message-----
> From: Jean-Baptiste Onofré [mailto:[email protected]]
> Sent: Saturday, June 18, 2011 10:18 PM
> To: [email protected]
> Subject: Re: Derby network server as a bundle
>
> Hi Scott,
>
> I created a bundle for derby-net:
> http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.derbynet/
>
> Regards
> JB
>
> On 06/19/2011 02:36 AM, Scott Came wrote:
>> Is there an existing implementation of a bundle that starts an instance of 
>> the Derby network server when the bundle starts?
>>
>> I know Derby is available as a bundle (I've already installed it)...I'm 
>> using the embedded server now but I think I may want to switch to the 
>> network server.  I'd rather have everything on the server living within smx 
>> (versus having to install and manage a separate database service).
>>
>> Thanks.
>> --Scott
>>
>
>
>

Reply via email to