"Kevin.Conner(a)jboss.com" wrote : There are other reasons why a process instance
is not guaranteed to work in a synchronous manner on the calling thread, such as timers,
human intervention, ESB invocations and possibly others. In general this is not something
that the invoker of the process instance can control.
For clarity to make sure I understand, let's say that we remove ESB from the picture
and we have a customer just using jBPM. They create a web application that accepts a
bunch of form data for a loan application and on submission, the web app creates a jBPM
process instance with the form data and signals it which does credit check, loan rate
calculation, maybe other steps, and then finishes by producing a loan result in a jBPM
process variable. 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.
Would we say that is improper use of jBPM and the web app should instead signal the jBPM
process in a separate thread, block the web app thread, implement the jBPM process with
some sort of callback at process completion, and wait for the jBPM process to call back to
the web application when it has completed so that the web application can get the jBPM
process variable with the loan result and render that in the page returned to the user?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199639#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...