Hi Ronald,
Just got back from some absence off work... anywayz...
kukeltje wrote : Just some wild guesses..
| - different (customized?) hibernate config?
| Nope plain config really.
|
| - Older and upgraded database model? e.g. one initially for 3.1?
just ran the setup sql script from
Just some wild guesses..
- different (customized?) hibernate config?
- Older and upgraded database model? e.g. one initially for 3.1?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4171473#4171473
Reply to the post :
anonymous wrote : The case i have is that Comment objects are attached to
tokens in the process instance.
I just tested GraphSession.deleteProcessInstance on a process with related
comments, and they were deleted just fine. This was with jBPM 3.2.3.
View the original post :
Same here. Works as expected
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4171066#4171066
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4171066
___
jboss-user mailing list
Hmm
Thats weird, we also use 3.2.3 here on a jboss server 4.2GA release and a mysql
database 5.x
No idea why the cascades dont work then on our installations
Regards,
Leo
mputz wrote : anonymous wrote : The case i have is that Comment objects are
attached to tokens in the process instance.
yes it will cascade
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4170710#4170710
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4170710
___
jboss-user mailing list
Hey,
I just wrote a handler to get rid of all the process instance data including
the cascades. The actual delete is kinda tricky in a sense that since all
collections and object properties are lazily initialized it requieres you to
load them up in a custom command object to get the actual
anonymous wrote : The actual delete is kinda tricky...
Why not simply use org.jbpm.db.GraphSession#deleteProcessInstance(long
processInstanceId) ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4170714#4170714
Reply to the post :
That wont work since you will have a non complete processinstance at your hands
caused by all lazy loading on the process instance...
Regards,
Leo
mputz wrote : anonymous wrote : The actual delete is kinda tricky...
|
| Why not simply use org.jbpm.db.GraphSession#deleteProcessInstance(long
lblaauw wrote : Hey,
|
| I just wrote a handler to get rid of all the process instance data
including the cascades.
Care to share what you did? I'm sure a fair few people would appreciate it.
It seems an big ommission if the one out of the box doesn't clean up properly
View the
Leo, the GraphSession.deleteProcessInstance method *should* handle all
references correctly, and should thus get rid of all data related to a process
instance. If it does not, it would be great if you could provide more info
about what is missed out, so that this can be fixed.
View the
Sure,
I dont claim this to be perfect but hey it works, so here is the code for the
handler:
| public class VerwijderProcessInstanceHandler extends JbpmHandlerProxy{
| private static final long serialVersionUID = -6125309218094541298L;
| /** Logger available to subclasses */
|
hey,
Well as you can see from my handler code above that is the only way I could get
GraphSession.deleteProcessInstance to delete the ProcessInstance and to have
the cascades work correctly. The case i have is that Comment objects are
attached to tokens in the process instance. Basically I had
Aha, ok.
So, the process instance is not deleted after it has been terminated?
Can I restart it, if I know its ID?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4170519#4170519
Reply to the post :
look at my last remarks about 'restarting' and yes you need something like the
id. Restarting from the beginning is *not* automatically done, unless you e.g.
move the root token to the start node, but behaviour would probably be strange
in some cases since there are already process variables
related to this topic I have been thinking about how to totally get rid of a
process instance from a db. Obviously there will be a lot of stuff hanging
around. If I were to perform a hibernate delete on the process instance would
it cascade and delete everything associated with the process
anonymous wrote : So, what happens with an ended process instance?
It stops running
anonymous wrote : Is still available
There is something in the database yes
anonymous wrote : and able to be restarted again?
Depends... you can make the end date of the process null, then it is 'running'
17 matches
Mail list logo
