You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by "Johnson, Eric" <Er...@iona.com> on 2008/07/15 04:01:49 UTC
OSGi APIs
Based on the examples in SMX 4 kit, it does not look like there is a need to use the OSGi APIs to deploy a service into SMX.
Is the recommended approach for deploying functionality into SMX 4 to simply use the CXF and Camel code natively? Should users be steered away from using the OSGi APIs?
Re: OSGi APIs
Posted by Guillaume Nodet <gn...@gmail.com>.
On Tue, Jul 15, 2008 at 3:56 PM, Johnson, Eric <Er...@iona.com> wrote:
> Thanks for the info Gert.
> Can I now just drop an xbean.xml file for the say the JMS BC into the
> deploy directory without needing all of the JBI packaging? Or is that a
> future feature?
Not yet. It will come soon, but this is not yet available.
> What is the NMR API? DO I need to write apps specifically to access it?
> Or can I create endpoints with special addresses that connect to it?
Usually, there's no need to write against the NMR api directly.
>
> Cheers,
> Eric
>
> -----Original Message-----
> From: Gert Vanthienen [mailto:gert.vanthienen@skynet.be]
> Sent: Tuesday, July 15, 2008 1:26 AM
> To: users@servicemix.apache.org
> Subject: Re: OSGi APIs
>
> Eric,
>
> Users can still access the underlying OSGi runtime and register services
> there, but I would suggest only doing that for low-level, system-like
> services. For an end user, we would definitely recommend using one of
> the more specific technologies.
>
> With ServiceMix 4, you can now create and deploy CXF or Camel bundles
> without having to go through JBI packaging, but you can also just deploy
> your existing (or new) JBI artifacts on it as well or just create a
> Spring configuration file in the deploy directory (like e.g. the
> activemq configuration file that comes with the SMX4 distribution). The
> NMR API and services will allow you to tie them all together.
>
> Regards,
>
> Gert
>
>
> Johnson, Eric wrote:
>> Based on the examples in SMX 4 kit, it does not look like there is a
> need to use the OSGi APIs to deploy a service into SMX.
>> Is the recommended approach for deploying functionality into SMX 4 to
> simply use the CXF and Camel code natively? Should users be steered away
> from using the OSGi APIs?
>>
>>
>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
RE: OSGi APIs
Posted by "Johnson, Eric" <Er...@iona.com>.
Thanks for the info Gert.
Can I now just drop an xbean.xml file for the say the JMS BC into the
deploy directory without needing all of the JBI packaging? Or is that a
future feature?
What is the NMR API? DO I need to write apps specifically to access it?
Or can I create endpoints with special addresses that connect to it?
Cheers,
Eric
-----Original Message-----
From: Gert Vanthienen [mailto:gert.vanthienen@skynet.be]
Sent: Tuesday, July 15, 2008 1:26 AM
To: users@servicemix.apache.org
Subject: Re: OSGi APIs
Eric,
Users can still access the underlying OSGi runtime and register services
there, but I would suggest only doing that for low-level, system-like
services. For an end user, we would definitely recommend using one of
the more specific technologies.
With ServiceMix 4, you can now create and deploy CXF or Camel bundles
without having to go through JBI packaging, but you can also just deploy
your existing (or new) JBI artifacts on it as well or just create a
Spring configuration file in the deploy directory (like e.g. the
activemq configuration file that comes with the SMX4 distribution). The
NMR API and services will allow you to tie them all together.
Regards,
Gert
Johnson, Eric wrote:
> Based on the examples in SMX 4 kit, it does not look like there is a
need to use the OSGi APIs to deploy a service into SMX.
> Is the recommended approach for deploying functionality into SMX 4 to
simply use the CXF and Camel code natively? Should users be steered away
from using the OSGi APIs?
>
>
>
Re: OSGi APIs
Posted by Gert Vanthienen <ge...@skynet.be>.
Eric,
Users can still access the underlying OSGi runtime and register services
there, but I would suggest only doing that for low-level, system-like
services. For an end user, we would definitely recommend using one of
the more specific technologies.
With ServiceMix 4, you can now create and deploy CXF or Camel bundles
without having to go through JBI packaging, but you can also just deploy
your existing (or new) JBI artifacts on it as well or just create a
Spring configuration file in the deploy directory (like e.g. the
activemq configuration file that comes with the SMX4 distribution). The
NMR API and services will allow you to tie them all together.
Regards,
Gert
Johnson, Eric wrote:
> Based on the examples in SMX 4 kit, it does not look like there is a need to use the OSGi APIs to deploy a service into SMX.
> Is the recommended approach for deploying functionality into SMX 4 to simply use the CXF and Camel code natively? Should users be steered away from using the OSGi APIs?
>
>
>