Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.3.2, 2.0.0
-
Fix Version/s: 3.0.0-M2
-
Component/s: Modules: BPM / Rules
-
Labels:None
-
Similar Issues:
MULE-1219Make Mule the default "MessageService" for jBPMMULE-5111Initialisation of a jbpm connector is not correctly handled with an already-initialized jBPM ProcessEngineMULE-5110Defining attribute "processEngine-ref" of connector "jbpm-connector" as IDREF in mule-bpm.xsd is too restrictiveMULE-927Axis connector uses local logic to set sync/asynchronous messaging instead of using environment's default settingMULE-1114Example app to illustrate using the BPM connectorMULE-3589Support the Synchronous to Asynchronous scenarioMULE-3212Upgrade jBPM to 3.2.2MULE-5555Allow users to pass wrapper parameters using the command lineMULE-5114Add support for jbpm 4.4MULE-5208problem using <mule-send> in jbpm 4.4 to call mule 3.0.1
Description
jBPM has a new (experimental?) concept called "asynchronous continuations" which are intended to better support process transitions fired by asynchronous messages. The Mule transport should probably trigger jBPM transitions via this new interface (if it is stable, that is).
http://docs.jboss.com/jbpm/v3/userguide/asynchronouscontinuations.html
Issue Links
| Related | |||
|---|---|---|---|
|
|
|
||
This feature at jBPM is nowadays not in experimental status. At jBPM 3.2.3 and the new jBPM 4 versions there are different ways to use this feature, using JMS and Database as MessageService. For example, if anyone download jbpm-jpdl-suite.3.2.3 and one look at jbpm.cfg.xml file it looks like:
<service name="message" factory="org.jbpm.msg.jms.JmsMessageServiceFactoryImpl" />
<service name="scheduler" factory="org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory" />
There is a "message" service deployed so, why can´t i use Mule as Message Service for jBPM?
If this feature is not implemented when you integrates Mule and jBPM you can´t execute any process that have asynchronous nodes neither asynchronous subprocesses. It is a hard limitation on Mule, don´t you think?
Regards,