One of the great advantages of BPEL is the graphical design environment. Easy to build a process and perfect to illustrate the working of the process, especially to end-users. But, there’s a catch! Not all changes in the XML-source code are reflected on the graphical end. There are a lot of actions you can take in the XML (all the bpelx: actions) that aren’t shown on the graphical side. Even worse: when you update them, they won’t always show up in the JAR file that’s generated. So keep in mind: if you make changes to your code in XML format, especially when you change bpelx: commands, DELETE your .jar file, so it’s rebuilt. Otherwise you’ll keep looking for that one error that’s no longer there!
Technorati Tags: bpel
December 27th, 2005 at 16:16:52
Is the problem you describe attributable to a specific implementation?
http://duckdown.blogspot.com/
December 28th, 2005 at 10:03:07
As we work mainly with JDev, I can only speak for that environment.
February 13th, 2006 at 05:02:48
& vice versa. Not all changes in the graphical end are reflected on the XML-source code .
e.g
1. modifications of the scope label in the graphical end will not change the source code.
2. Sometimes, deletion of the correlation set, property and property alias in the graphical end will not change the source code.
April 15th, 2006 at 15:59:39
Hi, you might also want to try eClarus Business Process Modeler that provides roundtrip engineering between BPMN – BPEL. In other words, you can visualize the BPEL artifacts using a much richer and standard BPMN notation.
eClarus Business Process Modeler comes three flavors; community , business analysts and SOA architects. Community is free and the other two have 15 days trial licenses and can be renewed. They are all Eclipse-based. Community and Business analyst version uses RCP and SOA is IDE-based. They are sharing the same models. SOA edition can be installed at the same IDE with Oracle BPEL designer.
Other use cases include 1) generating WORD-based process design doc 2) user-defined properties (UML profile like mechanism) 3) Import from Rose and UML2 4) Track changes for AS-IS and To-Be models 5) Model validation
You can get more BPMN information from http;//www.bpmn.org and get free download from
http://www.eclarus.com