websphere - How does the shared engine look up the required resources for a process step invocation? -
i using shared process engine on websphere , want understand how engine looks required resources (custom code shipped process application) process step invocation. thread context switch applied?
the shared process engine can used multiple applications, 1 of these applications being camunda webapplication.
whenever process engine "does something" within process instance, such executing service task, performs thread context switch. thread context switch performed application deployed bpmn process engine executing. necessary process engine able use resources locally available within application.
examples these kinds of resources:
- the application's classloader, in order instantiate java delegates
- the application's cdi bean manager, in order able invoke cdi beans.
how "thread context switch" work technically?
process engine executes callback method on ejb has included within application. why include camunda-ejb-client.jar. relevant information: process engine invokes local business interface of ejb.
result, thread context switch performed ejb local invocation semantics. whatever websphere puts in place ejb local invocation work , whatever websphere not put in place ejb local invocation not work.
behavior same if put code java delegates ejb local business interface , invoke application.
Comments
Post a Comment