Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.0
-
Fix Version/s: 3.0.1
-
Component/s: Modules: BPM / Rules
-
Labels:None
-
Environment:
Windows XP SP3 32bit
Sun JDK 1.6.0_21
JBoss AS 5.1.0
-
User impact:High
-
Configuration:
-
Log Output:
-
Similar Issues:None
Description
The initialisation of a jbpm connector is not correctly handled when a reference to the already-initialized jBPM ProcessEngine is injected by Spring by reference through the attribute "processEngine-ref" of the connector.
In class org.mule.transport.bpm.jbpm.JBpmConnector, the method createBpms()
@Override
protected BPMS createBpms() throws Exception
{
return (BPMS) ClassUtils.instanciateClass(JBPM_WRAPPER_CLASS, configurationResource, processDefinitions);
}
should be replaced by
@Override
protected BPMS createBpms() throws Exception
{
BPMS bpms = null;
if (processEngine ==null)
{
bpms = (BPMS) ClassUtils.instanciateClass(JBPM_WRAPPER_CLASS, configurationResource, processDefinitions);
}
else
{
bpms = (BPMS) ClassUtils.instanciateClass(JBPM_WRAPPER_CLASS, processEngine);
bpms.setProcessDefinitions(processDefinitions);
}
return bpms;
}
Otherwise, Mule is trying to initialise the connector afterwards with an inexistent applicationContext.xml file when the method ((org.mule.api.lifecycle.Initialisable)bpms).initialise() is called and a org.mule.api.lifecycle.InitialisationException is then thrown.
Activity
Bertrand Gillis
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Attachment | mule-transport-bpm.zip [ 12997 ] |
Daniel Feist
made changes -
| Fix Version/s | Bug Backlog [ 10522 ] | |
| Assignee | Travis Carlson [ tcarlson ] | |
| Priority | To be reviewed [ 6 ] | Major [ 3 ] |
Travis Carlson
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Travis Carlson
made changes -
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Fix Version/s | 3.0.1 [ 10877 ] | |
| Fix Version/s | Bug Backlog [ 10522 ] | |
| Resolution | Fixed [ 1 ] |