Hi Reju,
I would like to say that this question is a "classical" one for all new
SMX4 users.
If you begin your developments on ServiceMix4, I think it's better to
begin with OSGi service bundles. This approach is interesting especially
if your underground application is already OSGi based. The disadvantage
of this is if you want to migrate your services on another JBI compliant
ESB (like OpenESB), you can't.
On the other hand, using JBI packaging (which works without problem on
SMX4/NMR), your services can work on any JBI compliant ESB (like SMX3 or
OpenESB). For example, in my case, I have "old" JBI services running in
production on SMX3. Before migrating these services into OSGi packaging,
I have directly deploy it in SMX4 (no change at all has been made).
I hope it's clear :)
Regards
JB
Mathew, Reju wrote:
Hi,
I am a newbe to the ServiceMix. When developing new applications (using
servicemix - camel) deployed in ServiceMIX 4, which is the preferred way
of packaging - JBI or OSGI ? Do not envisage registering at / using
(OSGI) Service Registry and either way packaged seems deployable into
the osgi container of servicemix (using osgi install) in the same way.
So then which way is recommended / forward looking approach ?
thanks,
Reju
