Hi Pieter, It is in general as it is specified in the Seam docs. One pageflow corresponds to one task or more general to one transaction that is important for the business process. This transaction generally involves getting from one wait state in the business process to the next. However, if you feel that other aspects of business process management, such as e.g. logging or history, are important in your particular use case, than it might make sense to define a business process parallel to your pageflow. But if this is not important to you, I wouldn't bother defining a business process.
Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107549#4107549 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107549 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
