This is indeed what I used something similar for in jBPM 3. It's not that difficult
since you can retrieve the processdefinition in xml as a resource from the deployment and
use xpath on it for retrieving the additional attributes.
What I did (amongs other things) was adding an attribute to a task with the average
duration (different from the duedate). Without extending the database, I was able to use
this.
Otoh, in jBPM 4 it is much easier to extend an activity then it was in jBPM 3 since there
is no database model to be extended. Just extend the activity and change the activities
xml config file and you are done. The two solutions can coexist without any problem,
although I think the activities config file was more for new node types than extending
existing ones.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258982#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...