Use or not to use JBI

[Michał Warecki]

I'm little cunfused in topic JBI. I've read Fuse documentation, Servicemix documentation and JBI specification and I totally don't know what to do

In most Fuse examples it is shown non-JBI Fuse usage and couple of JBI examples but in Fuse/Servicemix description is that JBI is one of its most important feature.

My question is : what are the advantages of JBI comparing to non-JBI usage. Why in most of the examples are shown non-JBI usage ?

If I have to provide integration infrastructure based on Fuse then should I use OSGi with JBI or rather without ?

Edited by: michal.warecki on Jan 23, 2011 6:31 PM

[Claus Ibsen]

Dont use JBI is the short answer. Its a dead spec.

Fuse ESB 3.x is based on JBI.

Fuse ESB 4.0 is re-architected based on OSGi. There is although support for JBI but it's an optional module.

You can read some thoughts from the lead-architect on Fuse ESB / ServiceMix here:

http://gnodet.blogspot.com/2010/12/thoughts-about-servicemix.html

[Michał Warecki]

Thanks for the great answer. What about NMR with non-JBI usage ? What are the benefits of using NMR ? Why should I use it instead of directly send payload from one endpoint to another ?

[Claus Ibsen]

The NMR offers you you the same benefits as the JBI NMR does.

The NMR in Fuse ESB 4.x onwards can exchange any kind of message payload.

Where as JBI its confined to be XML messages only.

There is some info here

http://fusesource.com/docs/esb/4.3/esb_deploy_osgi/Nmr.html

And you can easily leverage the NMR between Camel applications

http://camel.apache.org/nmr

Some users dont use the NMR but exchange data using JMS messages instead. That's also a viable solution.

[Michał Warecki]

Thanks for the helpful answer.

[James Peterson]

I agree . very usefull topic