"camunda" wrote : | apestel wrote : | | When the process finishes (signal returns after couple seconds), the web app extracts the loan result from the finished jBPM process and displays it in a web page to the user. | | | This is a common discussion. Basically you should not tightly couple the process with the user interface. As Kevin wrote, other things can happen in between that interrupt normal process flow. Another argument is, that you want to gain flexibility in changing your business processes. For example you change the loan application to include a human task in some cases. Now you have to change your web application too! But you shouldn't! Better is some kind of generic piece of software in the web application that somehow can handle the "result" of the signal (wait-state x, ended, ...) in a generic way... | It's actually more fundamental than jBPM: within the ESB we've been trying to encourage a more loosely coupled, message-driven approach for years. Within the industry we've been doing it for much longer. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200088#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...