Yes, although I think your definition of public differs from mine here. The
JbpmContext is normally the api to direct the engine. But you can use the
ProcessDefinition object and all related objects to create one and deploy it.
You could also have your code generate an xml document. The latter
Thanks, using the ProcessDefinition object will work for me. However, why
would it be easier to create the xml document? I would hoping to just pass the
ProcessDefinition object itself to something.
View the original post :
passing the ProcessDefinition will work and it was just my opinion that it
would be easier to create the xml document. No special reason to do that, or it
migh be that if it is stored, it can be looked up, changed and redeployed
again. But if you feel comfortable using the PD, then go
