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

As a user I want to be able to know in advance what will be the data type returned after a message transformation

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

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 3.3 M3
  • Fix Version/s: 3.3 M3
  • Component/s: Core: Transformers
  • Labels:
    None
  • User impact:
    High
  • Affects Docs:
    Yes
  • Similar Issues:
    None

Description

Mule currently manages transformations in a weak way, one of the main problems is that it does not enforce the application of transformers on a given message, so is not possible to know in advance what would be the payload type of a message after a given transformation.

Problems:

  • Given a transformer chain, you cannot know in advance what will be the data type of the payload after the transformation.
  • Because transformers are just skipped with no error, users can think they are doing everything ok and then found an error later on the flow, making the error analysis hard.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-6048 Transformer API is inconsistent

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Bug - A problem which impairs or prevents the functions of the product. MULE-6047 Application of a transformer chain to a mule message can produce different return types

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds
Pablo Kraan made changes - 22/Mar/12 11:24 AM
Field Original Value New Value
Priority To be reviewed [ 6 ] Critical [ 2 ]
Pablo Kraan made changes - 22/Mar/12 11:25 AM
Resolution Fixed [ 1 ]
Fix Version/s 3.3 M3 [ 11124 ]
Status Open [ 1 ] Closed [ 6 ]
Pablo Kraan made changes - 28/Mar/12 03:27 PM
Link This issue relates to MULE-6048 [ MULE-6048 ]
Pablo Kraan made changes - 28/Mar/12 03:28 PM
Link This issue relates to MULE-6047 [ MULE-6047 ]

People

  • Assignee:
    Pablo Kraan
    Reporter:
    Pablo Kraan
Vote (0)
Watch (0)

Dates

  • Created:
    24/Feb/12 07:33 AM
    Updated:
    28/Mar/12 03:28 PM
    Resolved:
    22/Mar/12 11:25 AM

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.