File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Web Services and the fly likes ServiceMix / Mule Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "ServiceMix / Mule" Watch "ServiceMix / Mule" New topic

ServiceMix / Mule

Walter Bernstein
Ranch Hand

Joined: Dec 19, 2007
Posts: 57
Hello Binildas!

in the book you are focused on ServiceMix.
Why did you choose ServiceMix instead of Mule?
Is it beacause of JBI support? Is JBI support important?

Binildas Christudas

Joined: Sep 02, 2002
Posts: 25
Hi Walter,

I have been closely observing the Service Oriented Integration space in Java world and hence we have been dealing with the following frameworks:

  • [list]ServiceMix
  • Mule
  • OpenESB
  • Celtix
  • Websphere
  • Aqualogic
  • Sonic
  • Fiorano
  • etc.

  • Amongst them, the first three are related to Java Business Integration (JBI) in some way and open source. The extend to which these three frameworks support JBI are varied, and let me explain a bit on that.

    OpenESB is Sun's Reference Implementation (RI) for JBI. Many downloads were done for technology validations. I am not ruling out the possibility of using OpenESB for production applications, but I am yet to get references for that.

    Compared to Mule, the major difference for ServiceMix is its architectural design, which is fundamentally based on the Java Business Integration (JBI) standard.

    Mule and JBI have some overlap in the problems they solve but under the covers they do it in different ways. JBI is XML and WSDL centric where as Mule makes no assumptions about the message type. JBI uses a notion of Message Exchanges and a Normalized Message to communicate between components, where as Mule use a "POJO / Endpoint" architecture. JBI is a service container whereas mule is more of a ubiquitous messaging fabric that goes beyond integration to provide a solutions for translating, monitoring, routing and orchestrating all type of information around the organization.

    Let me now point to few On-Line articles/discussions. The first link is a "must read", since it narrates discussion happened between the creators of ServiceMix & Mule:
    ServiceMix & Mule

    As you have already noticed, the book is on JBI and an open source implementation for that. JBI as a technology and as an API is relatively new, but is very promising on SOA and integration point of view. There are no other books available on JBI at present. Moreover, we wanted to create a book for developers. This means, readers need to understand JBI API, then use an implementation and try out things at code level. Obviously we can use Mule or ServiceMix for that. Now, as we discussed above, ServiceMix is built from the ground up on JBI principles, patterns and abstractions rather than tacking JBI onto the side of a quite different model. This is the main reason why we chose ServiceMix.

    To learn more on ESB, JBI, ServiceMix & EIP, refer to the PACKT title "Service Oriented Java Business Integration":

    Binildas C. A.<br />Principal Architect, <a href="" target="_blank" rel="nofollow"></a><br />(SCJP, SCJD, SCBCD, SCEA, MCP, TOGAF, LZA)<br /><a href="" target="_blank" rel="nofollow"></a>
    Walter Bernstein
    Ranch Hand

    Joined: Dec 19, 2007
    Posts: 57
    Thanks for the response!
    It is sorta covered in the JavaRanch Style Guide.
    subject: ServiceMix / Mule
    It's not a secret anymore!