"kukeltje" wrote : all docs about jBPM assume this behaviour, so it is very
hard for us to point to something specific other than the normal docs.
i can't find smth about this in doc (jbpm4) at all - neigher in "state" section
nor running/finding process instances.. where is this behaviour descr
"kukeltje" wrote : yes, that is normal jbpm behaviour.
can you link to doc describing that situation, please. probably, i made smth
wrong like params or configs
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266968#4266968
Reply to the post :
http://www.jbos
"kukeltje" wrote : Yes... but is it IN your database
Is it possible to have process just in the same state as before restarting?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266957#4266957
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=pos
"kukeltje" wrote : Yes... but is it IN your database
Is it a bug or feature? Please, give a link to doc, if it is documented.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266956#4266956
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=postin
The problem is that the process in wait state ("state" element) can not be
found after application server restart, where application with jbpm is deployed:
Searching of process looks like this:
--
String processInstanceRefId = getProcessInstanceRefId(context, messageKind); //
(G
