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

[estaub]

In case it wasn't clear...
My note about the mismatch between BPMN and JPDL was in no way meant to discourage mapping from B to J.  I'm going through the same process as Jeff.  I was only saying that introducing use of BPMN terms into the execution domain, e.g., as the basis for names in an API, would be a really bad idea.

Re use of GPD... I'm pretty unhappy with GPD.  The code base is not very extensible, and is highly dependent on the XML editor codebase.  

I went to the talk by the Eclipse BPMN editor guys at EclipseCon, and was very sold on GMF.  The BPMN editor is really slick, and easily extensible.  People kept complimenting them on this or that feature, and they kept saying things like "well, it wasn't really a requirement, but all we had to do to implement it was write these 5 lines of code, so we just threw it in."  High praise for the framework!  

After spending some time with the code, I am even more sold.  I would very strongly suggest that Koen look at GMF et al again - it's probably grown up a lot since he checked it out the first time.

-Ed

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

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