i didn't yet get to mention my view on how we should support BPMN. I think we should have a (one-way) BPMN to jPDL export functionality in the STP BPMN designer. That fits right into our vision and strategy. Analysts can then model freely in BPMN. When they're done, they can give that BPMN analysis model as part of the requirements input to the development team. Then the development team can do an export to jPDL and further make the process executable. After that, further iterations all happen on the jPDL executable process. The analysts will now still recognize the jPDL diagram. They still can discuss it. But further iterations will not be synchronized back to the original BPMN analysis model. (just like no one would keep their analysis UML class diagrams in sync with the implementation UML diagrams.) Once the tranlation is done to an executable process language, it becomes software is it comes under the control of the development team. That is the bigger picture in which I see the value of a BPMN to jPDL export functionality. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164955#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...