Hi Aarna,
it's always difficult to compare two solutions, especially in the open
source world.
Nevertheless, I would like to give you my point of view (it's only my
modest one):
- JBoss ESB is linked to JBoss Application Server. The default JBoss ESB
distribution embed the JBoss AS. It allows the ESB to use the
transaction layer of the AS as when you deploy SMX into an application
server. But on the other hand, if you need a lightweight ESB, SMX is
better as you can launch as standalone
- as far as I know, JBoss ESB is not linked to any norm. SMX is built on
ground of JBI specifications and SMX4 uses an OSGi kernel.
- the JBoss ESB components is not very large: you can use JMS;
WebService, BPEL, email, filesystem, database. You don't have any
solution to implement advanced EIP as Camel does in SMX.
- JBoss ESB has a good BPEL integration including WS-BPEL and jBPM.
- JBoss ESB has a good graphic management tool.
From my point of view, JBoss ESB is mainly oriented to BPM usage. It's
not efficient in the mediation layer as SMX is.
It's only my point of view.
Regards
JB
iamaarna wrote:
Hi
We are evaluating JBOSS ESB and Servicemix. I am biased towards Servicemix
because of its rich support for integration patterns provided through camel.
I think JBoss does not have XSLT support. However I need more reasons that I
can use to convince my boss for using Servicemix. Can the users help ?
Aarna
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
[email protected]
PGP : 17D4F086
