That's a good point about multiple languages executing on th same engine. Of course, once a CIO starts thinking of something as a 'BPM" solution, it's not always easy to convince them that we should be using two different process definition languages instead of just one. anonymous wrote : XML schema types, WSDL definitions and structured constructs aren't in the vocabulary of business analysts.Indeed, with BPEL a developer would have to provide partner services (dealing with all the WSDL stuff, etc.) for use in the parent process by the analyst; and actually, the analyst would still need to become a bit more "technical".
It might also be difficult to rule out any need for a simple user interaction or two in the parent process--at which point it becomes difficult for BPEL to make the grade. With BPEL as the parent process definition lanquage, all human tasks would need to be relagated to a sub-process (of some sort), even the simplest ones. Oracle's BPEL product exemplifies this by supplying a pre-built web service that handles human tasks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912738#3912738 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912738 ------------------------------------------------------- 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
