[jbpm-dev] [Design of JBoss jBPM] - Re: jPDL 4 early feedback

[heiko.braun@jboss.com]

Maybe it helps if we regard jpdl4 with the core bpm constructs in mind for now. Control flow activities that is. I think this part needs to be stable before being released whereas use case activities are more likely subject to change and can easily be added along the way. 

Let's do an example: We ship a stock "email" activity that's being represented by an email element in schema. Later on someone contributes an FTP activity to jBPM. At that point we already have stock activities being treated differently, because we cannot simply change the jpdl4 schema. 

If we use one way to express extension points, and that's equal to both stock and custom extension, then we don't run into this problem. 

Basically I am trying to get to the point where we have a clear way of extending jdpl4. Both for jpdl4 developers as well as users. 

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

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