Of course I have done this extensively before posting to this mailing list.
But this solution isn't working for me because i don't know the names of the transitions in the handler class. We are trying to build a generic system (we create processdefinitions on the fly) and cannot create specific classes for each process.
That is why I wanted the "handler" functionality on the transition conditions and not on the decision node level.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250823#4250823
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250823
steeqs4, if you could answer, I would be interested in what you did with Glassfish/BPEL, since Glassfish is my target :
_ did you need additional components to Glassfish ? like OpenESB ?
_ does your solution have a persistence service ? (or something that remembers when a process was stopped in case of failure or so)
_ did you find sufficient documentation ?
_ except it is not BPMN, are you globally satisfied with this solution ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250819#4250819
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250819
The position of the PVM has not changed, it just does not have a separate project anymore.
jBPM is the project. It contains several 'modules' jPDL and BPMN2 (under development) are process 'languages' based on the PVM which is another one of these 'modules'. The PVM can be used completely independent of jPDL, BPMN2 etc
Btw, all pvm classes are 'internal'. The reason for this is that they should not be used by people using jPDL or BPMN2, but for people developing their own languages you do not have much choice ;-). Sure some things might change in the future, but not drastically.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250818#4250818
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250818