Uploaded image for project: 'Mule'
  1. Mule
  2. MULE-1221

BPM transport should use dynamic:// transport instead of MuleClient for dynamic endpoints

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix or Usage Issue
    • Affects Version/s: 1.3.2, 2.0.0
    • Fix Version/s: None
    • Component/s: Modules: BPM / Rules
    • Labels:
      None
    • Similar Issues:

      Description

      If "useLocalEndpointsOnly = false", the BPM transport allows a process to send messages to any endpoint (i.e., not limited to the outbound endpoints on a component) Currently, an instance of the MuleClient is used for this, but it would be cleaner to use the "dynamic://" transport (MULE-970) and thereby eliminate the dependency on (and instance of) MuleClient.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tcarlson Travis Carlson
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: