Thanks for the quick response. It would be nice to model the entire process using one process-definition, but the separation of workflow and web service orchestration is acceptable.
In your opinion, is JBoss jBPM mature enough to handle the combination of workflow (jPDL) and web service orchestration (BPEL) in a real world environment (such as a bank's business process)? When is a good time for businesses to jump on the open source BPM wagon? Thanks for the blog article, it is quite enlightening. How does JBoss Stream framework fit into this whole jBPM picture? Does Stream interface with jPDL easily for portal development? I still think bringing together jPDL, BPEL, and Stream? into one model would be wonderful. Time for a rhetorical question. Is JBoss adopting BPM technologies and standards that will stand the test of time? There are just too many BPM implementations (e.g. BPMN, XPDL, ...). Sorry for fishing with so many lines! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023991#4023991 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4023991 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
