Mule
  1. Mule
  2. MULE-1221

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

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor 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:
      MULE-5162Dynamic endpoints don't work for VM and JMS transport
      MULE-6552XMPP doesn't support dynamic endpoints
      MULE-2593Transformer for allowing dynamic addressing in HTTP transport
      MULE-3650BPM transport cannot handle spaces in the process name
      MULE-4743MuleClient.send() timeout is not respected with http transport
      MULE-2592Dynamic addressing for Pop3 dispatcher
      MULE-5134When multiple connectors are specified dynamic endpoints errors.
      MULE-6200Binding does not work with dynamic endpoints
      MULE-5523Using dynamic endpoint produce error when using async response
      MULE-1881Cannot dynamically create rest endpoint

      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.

        Activity

        There are no comments yet on this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development