"plalloni" wrote : Ok, we solved it!
Glad to hear it!
"plalloni" wrote : we didn't see the part of docs where it says that we must
persist process definition before its instances.
This is a subtle one. The database example in Chapter 3 of the jBPM user guide
starts with saving the definition...
Ok, we solved it!
The problem dissappeared by doing 2 changes to our code:
1. Persisting the process definition before saving the process instance
2. Putting calls to beginTransaction() and commitTransaction() around the
saving of the process instance (and around the saving of the process defin
"[EMAIL PROTECTED]" wrote : I'm investigating the problem. In the meantime
please tell me the version you are using.
JBPM 3.0.2
"[EMAIL PROTECTED]" wrote : Another question: does your code snippet work with
Hypersonic?
With Hypersonic the same problem is reproduced
View the original post :
h
Another question: does your code snippet work with Hypersonic?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915389#3915389
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3915389
--
I'm investigating the problem. In the meantime please tell me the version you
are using.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915388#3915388
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3915388
---
I ran into a similar problem when using the Hypersonic database within jBoss
and my temporary solution when saving a ProcessDefinition was to catch the
exception that is generated during the commit.
As in:
jbpmSession.beginTransaction
jbpmSession.getGraphSession().saveProcessDefinition( pd )
tr
Well... we really don't want to switch BPM engines ATM so here is my stack
trace. As can be seen, the error occurs when I try to ask a ContextInstance
from my just loaded ProcessInstance, obviously the problem refers to hibernate
lazy loading but since I'm not familiar with JBPM hbm mappings I r
Unfortunately I haven't, because we've abandoned the whole jBPM and Implemented
our own workflow solution. Because it seems that the jBPM is still immature and
bug infested.
Good luck
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915306#3915306
Reply to th
I wonder if you solved this issue and how you did it since we're having the
very same problem right now and we're completely lost...
Have you?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915302#3915302
Reply to the post :
http://www.jboss.com/index.html
