Here is a scenario that may lend to the discussion-- A good sized business process is broken out into many sub-processes, and the entire process is "handled" in two tiers. The first tier is handled primarily by a business analyst, and is responsible for overall orchestration of second tier processes. Second tier processes may involve various integrations or complicated transformations, etc. and are worked primarily by developers.
A second tier process may involve a complicated user interaction. Should the same process engine that is responsible for orchestrating the entire parent process also be the flow engine behind the flow of the UI, or should the developer use some other web framework to define screen flow? The trend is toward one core engine being used for all kinds of flow. By properly defining sub-processes, separation of concerns can be accomplished as a matter of policy and tooling. If a process definition language can "do it all", it is simply important that "best practices" be defined to help ensure the success of users and fend off criticism. Yes, I know it looks like this post conflicts with my previous one, but hey, I'm thinking out loud. ;-) -Britt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912696#3912696 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912696 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
