"JBPM generally takes this approach - if multiple nodes and transitions can be
executed synchronously, by default it won't commit any until all are done."
Can you tell me how to change this default behaviour of jBPM?. I want to save
the processinstance after execution of each node. Can i do anyt
Oh jesus, what a complaints.
Yes they can, by not declaring variables on the tasknodes you have access to
the processcontext variables. Those are shared
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048150#4048150
Reply to the post :
http://www.jboss.c
There several actors do the workflow instance in the same phase of node or
different task which execute by different swimlane. in that case, taskvariables
can't be shared ?
the context can not be shared ? oh My God.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtop
The context should not be shared!!! Open it and close it per webrequest as you
mention further on. What do you mean by different PO's for different clients?
Do they all work on the same processinstance at the same time? Or do you have
multiple tasks parallel tasks for different actors? In that
Creating a jbpmContext is a lightweight operation, basically it is a wrapper
for a Hibernate transaction. ? I was confused before . now I see.
persistence object ? I know it is a good idea, I mean the web application
close the context after the processinstance.close(); so the whole wor
cron,
I think the key question is: "what happens next"?
If you're going to synchronously continue processing on the same process
instance, then did you really need to commit it to the db at this point in
time? If not, then don't do anything - just close it later. JBPM generally
takes this app
So you want a webapplication with saving all data each step but without any
overhead. Keeping a context open lead to lots of other issues with
none-connection oriented webapps. e.g. When do you close it if the user just
click the x on his browser? When the session times-out? In that case it is a
Creating a jbpmContext is a lightweight operation, basically it is a wrapper
for a Hibernate transaction.
Regards, Martin
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047532#4047532
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting
I have seen the javadoc before, and I can't use jbpm in that way because if you
close a jbpmContext, you must reactive it by call createJBpmContext(), which is
a resource costing process for applications. if we do that, the system will be
very slowly.
our system have 100-300 clients accessed co
Look at the javadoc for JbpmContext to see the correct usage of JbpmContext.
jbpmContext.close() should always be called within a finally clause. This
ensures that the Hibernate session and connection is properly closed.
Regards, Martin
View the original post :
http://www.jboss.com/index.html?
10 matches
Mail list logo
