[jboss-dev-forums] [Design of JBoss jBPM] - Re: Defining the API Mission

[heiko.braun@jboss.com]

anonymous wrote : 
  | BPMN is not a proven concept.
  | 

Tom, maybe you got me wrong here. I am not talking about BPMN or BPEL as a whole. When I say concept, I mean the BPMN composites. I.e. gateway, signal, event, whatever. They all have distinct meanings and an established name. 

So instead of naming it a decision, you could call it exclusive gateway right away. The reason why I prefer BPMN glossary over jBPM terms is that these people did a good job finding terminology and add short, descriptive explanations to the core concepts. Whereas in the PVM, we still have 3 or 4 kinds of "Executions".

If we could manage to become explicit in our jBPM4 terminology the same way, then I wouldn't complain. But currently I see a 200 pages document with very precise terminology (BPMN) and a redundant, hard to understand API (PVM) which is only obvious to it's inventor. 

So give me one good reason why we should chose the hard way and try to be superior to the BPMN spec leads and come up with something on our own.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166903#4166903

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166903