At Delphi Corporation, we are considering methods for committing to jBPM as a standard for J2EE development that requires BPM moving forward, and how what might be a best practice approach for implementing jBPM in a SOA sort of setting.
We are concerned that if we have a single jBPM logical service in an SOA, how we will have a clean deployment and wire protocol communication between deployed process definitions and the applications using the jBPM service remotely? Will we have to implement a communication framework (maybe SOAP) that all process definition handlers will have to use to do application/domain specific synchronous functionality (or asynchronous, for that matter)? What architectural approaches have people implemented? What specific technologies have they used? Is SOA a bad idea for jBPM - and if so, why? Will we have to implement a communication framework (maybe SOAP) that all process definition handlers will have to use to do application/domain specific synchronous functionality (or asynchronous, for that matter)? Additionally, is there a suggested approach for modeling every UI screen with a node in the process definition? We need to define standard approaches to the process definitions as well - and this is a contested topic for a number of reasons in our group. Any and all architectural appoaches and ideas would be helpful. Thanks, James View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951689#3951689 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951689 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
