Red Hat Bugzilla – Bug 779723
jBPM JCA inflow needs to support JMSProviderAdapter
Last modified: 2010-07-12 14:06:16 EDT
Date of First Response: 2010-05-31 01:57:17
Link: Added: This issue depends JBESB-3317
Code has been changed in ESB codebase but still need a docs update.
The adapter can be initialised in JNDI by including something similar to the following MBean within jbpm-service.xml.
<mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=RemoteProviderLoader">
This can then be referred to from within jbpm.cfg.xml and the inflow activation spec, for example the message configuration could be as follows (scheduler is similar)
<field name="providerAdapterJNDI"><string value="RemoteProviderAdapter"/></field>
More information need for release notes:
JMSProviderAdapter is now supported by jBPM JCA inflow.
Needed: What is the usecase that this enables ?
This allows the jBPM JCA inflow to be refer to JMS providers which are located in a JNDI context other than the current one, i.e. hosted on a remote system.
Added to the SOA 5.0.2 release notes as resolved:
JMSProviderAdapter is now supported by jBPM JCA inflow. This allows the jBPM JCA inflow to be referred to by JMS providers which are located in a different JNDI context to the current one, such as on a different server.
Has this been added to the community docs yet? Please let me know and I will then add it to the product docs.
The platform documents differ from the project documentation in this area. The project Administration Guide will be modified to include the text as included within JBESB-3363.
This information has now been added to the product Administration Guide. The Release Note has also been amended to point to it.
Verified int he SOA-P product docs here: