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-4646

When sync endpoint and disableTempDesintations are used together JMSMessageDispatcher should return null rather than NullPayload

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

Details

  • Type: Improvement Improvement
  • Status: Reopened Reopened
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 2.2.3 (EE only)
  • Fix Version/s: 2.2.4 (EE only)
  • Component/s: Transport: JMS
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    None

Description

This is because in this case no response is expected and therefore the service should behave in the an "outbound aysnc" mode and return the result of component inovcation and not the NullPayload response from outbound.

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Java Source File
    JmsResponseTransformerTestCase.java
    21/Dec/09 11:31 AM
    0.8 kB
    Puneet Gupta
  2. XML File
    responsetransformer-test.xml
    21/Dec/09 11:31 AM
    2 kB
    Puneet Gupta

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds

People

  • Assignee:
    Daniel Feist
    Reporter:
    Daniel Feist
Vote (0)
Watch (2)

Dates

  • Created:
    03/Dec/09 04:11 PM
    Updated:
    28/Dec/09 09:22 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.