Hi,
Like in my first post, normally i don't suggest you save process instances
during executions. when you issue an open session, it actually assigns a new db
connection for it. so in your process execution you are actually calling
different connections per each transition (unless you use getCurrentSession so
it will use the same connection) I don't know what kind of effects it will
give you, but i know it isn't desirable. If you want to observe a node, try
state instead of node. A state node is a wait state whereas a node continues
execution. Normally in your application, you have a servlet or a session bean
that loads the processinstance. Place your persistence routines in there (save
only once). Does this makes sense?
Regards,
Elmo
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918291#3918291
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3918291
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
