I am deploying processing programatically:
try/catch removed for clarity:
JbpmConfiguration jbpmConfiguration;
jbpmConfiguration = JbpmConfiguration.parseResource(jbpm.cfg.xml);
ProcessDefinition procDef = ProcessDefinition.parseXmlResource(mapName);
JbpmContext context =
For clarification, what I mean is lets say one of my nodes looks like this:
So version 1 of this definition would have node name GenerateETOWorkOrder in
the database.
Then lets say I edit the WF XML and
For clarification, what I mean is lets say one of my nodes looks like this:
state name=GenerateETOWorkOrder
| event type=node-enter
| action
class=org.openitsm.sr.workflow.WorkFlowActionHandler/
| /event
| transition to=end/
|
the save() method on the JbpmContext class accepts an instance to be saved.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3934947#3934947
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3934947
Thanks :)
Worked like a charm
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3934539#3934539
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3934539
---
This SF.Net email
Hi,
I downloaded jBPM 3.1 (starters kit) and am trying to get a stand-alone proof
of concept working and I got it to run fine with the default Hypersonic DB.
Now I am trying to get it to work with Oracle. I noticed that the starters kit
did not include a Oracle DDL script like there is for
The wiki is probably not up-to-date. Have a look at the docs :
http://docs.jboss.com/jbpm/v3/userguide/thejbpmdatabase.html
This describes the process for PostgreSQL and for MySQL. Oracle is just
analogous...
As I mentioned in my post I read that document and I understand it, the problem
is
Hi,
Sorry if this is a dumb question but in most code examples Ive seen a process
is advanced by calling processInstance.signal() and that works fine in my proof
of concepts. However lets say there is an issue where node a branches to
node b and c. How can I access b and c tokens