Details
Description
The issue of having these 2 methods throw an UOE is that they are called by Mule itself, like in DefaultMuleEvent.getMessageAsString(enc).
I don't think it is a correct behavior for Mule to trip on its own UOEs.
The issue of having these 2 methods throw an UOE is that they are called by Mule itself, like in DefaultMuleEvent.getMessageAsString(enc).
I don't think it is a correct behavior for Mule to trip on its own UOEs.
What are the locations that triggered it? Any sample configs? I don't see how Mule can return a string representation of a payload which can be multiple totally different payloads under the hood.