JIRA

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
  • Create Issue
  • Mule
  • MULE-1221

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

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Closed 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:
    None

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

  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds
There are no comments yet on this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Travis Carlson
Vote (0)
Watch (0)

Dates

  • Created:
    27/Nov/06 03:59 AM
    Updated:
    04/May/10 02:24 PM
    Resolved:
    04/May/10 02:24 PM

Agile

  • View on Board
  • Atlassian JIRA (v5.0.7#734-sha1:8ad78a6)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.