[jBPM] - Re: Exposing WorkItemHandler as an EJB (3.1) and referencing that work item handler from the BPMN process definition

Lukasz Zdobylak <[email protected]>
Newsgroups gmane.comp.java.jboss.user
Message-ID <[email protected]>
Lukasz Zdobylak [https://community.jboss.org/people/lukasz.zdobylak] created the discussion

"Re: Exposing WorkItemHandler as an EJB (3.1) and referencing that work item handler from the BPMN process definition"

To view the discussion, visit: https://community.jboss.org/message/828119#828119

--------------------------------------------------------------
Thank you for fast response.
We have few issues here 
1) when we have jboss as 7, the modules deployed don't have static name (those are extracted in directories which names are hashes) 
2) we need to dynamically deploy processes (and service impl) to the working instance of jboss brms and restarting brms is rather unacceptable. (there are many applications that would use brms).

Can you also help me understanding how jbpm works in context of the Threads?
I mean I am not sure if jpbm is fully operational service which manages own threads or it is using threads of clients which are calling some methods?
Eg when we start process instance from REST if it is started in thread managed by business-central, but when process reaches wait state (asynch service without completeWorkItem) and then external service wants to completeWorkItem, the process will continue in external service thread?
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/828119#828119]

Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2034]

_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.