BPEL, Java Developers take note….

I came across this interesting article by Matjaz B. Juric on how to integrate BPEL(Business Process Execution Language) into an SOA environment.
Juric discusses the core concepts involved with BPEL and why BPEL is so important.  He uses a business travel system as an example.

 Juric concludes by stating:

We have seen that BPEL is one of the most important cornerstones of SOA. It differs from common programming languages, such as Java, and is relatively easy to learn and use. Because BPEL has been designed specifically for definition of business processes, it provides good support for various specifics of business processes, such as support for long running transactions, compensation, event management, correlation, etc. BPEL is well suited for use with the Java EE platform, and many BPEL servers build on top of it. Java developers, particularly those who are involved in the development of enterprise applications and SOA, should therefore take a closer look at BPEL and start using the benefits it provides.

I have not used BPEL in any of the projects that I have been involved with but it certainly looks like something that should be seriously considered.

Does anybody have any Caveats from their experiences of using BPEL?  If so please leave a comment as I would be interested to hear any real world experiences. 

  1. #1 by Paul Browne - Technology in Plain English on July 20, 2006 - 2:08 pm


    If you’re interested in BPEL, you could do worse then check out the JBoss implementation – it comes with a nice (Eclipse based editor), looks a bit like Visio.

    Basic idea is that you draw your workflow diagram, it gets executed and fire events at each stage in the flow. You can then attach Actions (similar to struts) at each event as required.


  2. #2 by Stephen Downey on July 20, 2006 - 2:15 pm

    Hi Paul,

    Thanks for the suggestion, JBoss definitely seem to have the definitive IDE for this. I have played around with it myself in the past but have yet to use it with any clients yet.


(will not be published)