Wednesday, March 31, 2010

RiftSaw Release 2.0.0.Final

Today the RiftSaw team released 2.0.0.Final. This release packs the following feature set:
  • WS-BPEL 2.0 OASIS standard and the legacy BPEL4WS 1.1 vendor specification.
  • JBossWS Native and CXF Web Service stack support.
  • UDDI registration of BPEL endpoints, and Runtime UDDI Endpoint lookup as preview feature.
  • Enterprise quality GWT based BPM console to manage process definitions and instances.
  • High level API to the engine that allows you to integrate the core with virtually any communication layer.
  • JBoss deployment architecture, enabling hot deployment.
  • Compiled approach to BPEL that provides detailed analysis and validation at the command line or at deployment.
  • Short-lived and long-running process executions.
  • Process persistence & recovery.
  • Process versioning.
  • Ant-based deployment.
  • Integrated with the JBoss ESB.
  • Eclipse-based BPEL designer and deployment, supported through JBoss Tools.
  • Runs in JBoss Cluster.
  • A good set of examples to help you get started quickly, including Sun's BPEL Blueprint examples.
Some good resources for this release are the Release Notes, the Getting Started Guide, the User Guide and JBoss Tools. To download this release see our download page:

The RiftSaw team,


  1. Hello Kurt,

    My congratulations! The feature list looks very nice!

    "JBossWS Native and CXF Web Service stack support." - do you have a new implementation of the ODE Integration Layer using JBossWS instead of Axis2?

    Also about the BPEL Editor. Last time I tried it it was not working on Galileo and was very buggy. One could hardly work with it productively, did you fixed it in Eclipse repository or you are maintaining your own fork of the Eclipse BPEL Editor?


  2. Thank you Renat, the team has been working hard :). And yes RiftSaw added layer which uses JAX-WS and a collection of WS interfaces, rather then tying you to a specific WS implementation. At the moment we have instructions for plugging in either JBossWS-native (the actual JBossWS stack) and CXF. We're try to come up with porting this feature back to ODE-2.x.

    As far as the BPEL Editor goes, the tools guys have been fixing things in their own repo, and added a feature to deploy processes in a jar, so we could completely hook into JBoss Tools development features (hit save and have it auto-deploy). I'm sure the bug fixes will be/are contributed back upstream however.

    If you need any help of have issues, come see us at the riftsaw forum:

    Also, we love contributors :), and one of the things we did to lower the bar of getting involved is to help create a maven based build for ODE. So hopefully we can grow the RiftSaw/ODE community.



  3. Hi Kurt!

    Congratulations on the first stable release!

    Between the announcement, and the DZone interview from 2010-04-02, one thing intrigues me about clustering. The announcement says:

    * Runs in JBoss Cluster.

    While in the interview:

    "Another area is clustering and failover support. Although not currently supported, RiftSaw will be focusing on these areas going forward."

    So what is the relation of 2.0.0 to JBoss cluster currently? E.g. does it provide for load-balancing SOAP requests coming to the Riftsaw endpoint, if these correspond to self-contained, short-lived processes (immediate request-response)?

  4. Thanks Olo, currently we made sure Riftsaw has no issues being deployed to a JBoss cluster, we are now working to also take advantage of clustering. For load-balancing soap requests we may always suggest using apache httpd, or a hardware loadbalancer but if you're interested discussing this then please start a thread on the forum.


  5. Kurt, I've started a new discussion on this subject: