Associate the integration control with the process definition, not the context class
loader
-------------------------------------------------------------------------------------------
Key: BPEL-224
URL:
http://jira.jboss.com/jira/browse/BPEL-224
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM BPEL 1.1 beta 2
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 beta 3
Earlier versions associated the integration control (which mantains the active jms message
listeners and the outstanding requests of a single process definition) with the context
class loader because there is one business process per web application. However, this
prevents code running outside of the web application (such as a job executor) from
accessing the integration control and manipulating the jms objects.
The proposal is to associate the integration control with the process definition instead
of the context class loader. This allows any code with knowledge of the process definition
to access the integration control. The job executor, for example, retains the token
identifier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira