"dkane" wrote : Let's assume we are using jBPM. One question is unanswered, I will ask it again. When we expose stateful bean as Seam component with scope = business process, it's persistence may be longer than session and continue across sessions/users , right ? An object can stay in the BUSINESS PROCESS scope for longer than a session, yes. I would avoid the word persistence, as it has a specific meaning in Seam/JPA. anonymous wrote : If we don't need this object when process ends, then we don't need it to be entity bean and stay in database afterwards. We don't care how Seam/jBPM saves state in context (maybe using the same database), maps table names, fields, etc. Is it good practice to use process-wide stateful bean in such manner, or Entity bean is still recommended ? If you don't need to persist your object using JPA, then it doesn't need to be a JPA entity (you may still need to map it to a database for JPBM to persist between server restarts, but thats another matter...) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058946#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...