Well,

I think you could easilly use a stateless session bean, when you save the 
process status after each call. A better way would be to expose a process as an 
statful session bean. An user could fetch such a session, process task nodes 
without saving the context (much faster) and after all work is done, persist 
the state finally.

M.A.Bednarz
Literadix.de

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3945972#3945972

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3945972


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to