Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.0.1
-
Component/s: Modules: BPM / Rules
-
Labels:None
-
User impact:Medium
-
Affects Docs:Yes
-
Similar Issues:MULE-3211 Implement "composite" component type
MULE-2580Introduce new Component interfaceMULE-2713Implement a "scripting" component type and update example/test file to use it.MULE-2843Inconsistent life-cycle method behaviour between component implementations e.g. seda/directMULE-2821Inconsistent component type nameMULE-3241GlobalReceiver of BPM Connector is throwing an ExceptionMULE-3321Implement Component Notifications
MULE-2719 Implement top-level (reusable) componentsMULE-899Create a generic provider for BPM Systems (non-BPEL process engines)MULE-2836BPM originating message responses are not routed properly
Description
Now that we have an extensible Component interface, we should implement a BPMComponent which will hide some of the mechanics of the BPM transport and make it feel "more natural".
Placeholders have been added for this in r11566