Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
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.