There is a difference between "one engine being used for all kinds of flow" and "one language to do it all". All kinds of flow boil down to a state machine and context associated with each instance traversing it. Yet the widely varying environment in which each flow operates fully justifies the use of different languages.
In your example I'd feel tempted to use BPEL in the first tier since 1) all the actors are systems, 2) subprocesses lend themselves well to be exposed as services and 3) the design discussions at this level will be more intense, and the fact it is a standard helps establish a common foundation. I'm not completely sure, tough, because XML schema types, WSDL definitions and structured constructs aren't in the vocabulary of business analysts. For the second case 'd go for something closer to my development environment, to ease the integration and transformation tasks, and with built-in support for human involvement. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912723#3912723 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912723 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
