[jboss-user] [JBoss Seam] - Re: entity's lifecycle and jBPM

My understanding is different. For instance once the author of a document completed with draft it might ask somebody to review the document. And the process of reviewing would be a normal business process. As the result of reviewing the document could be promoted to the next state. But, when it is being promoted the action assigned to the transition could perform whatever we want, for instance inform the people interested in the traking the document about the the fact that the document has been promoted. That's why I believe jBPM suites. Lifecyle is similar to state-diagram or timeline (It's matter of taste). I'd prefer not to see tasks in the Lifecycle graph. And what is important user can be happy looking at the picture. Tasks make the picture overcomplicated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072239#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...