[
http://www.mulesource.org/jira/browse/MULE-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32313#action_32313 ]
Travis Carlson commented on MULE-4104:
--------------------------------------
http://fisheye.codehaus.org/changelog/mule/?cs=15990You can now do this, but you need to call AbstractExceptionListener.setReturnMessage(message) from within your exception strategy.
For 3.x it would be nice to simply add an optional return message to the ExceptionListener method:
public MuleMessage exceptionThrown(Exception e)
However, I didn't do this for 2.2.x so as no not break the API.
> Returning an error message as the payload from an exception strategy currently does not work
> --------------------------------------------------------------------------------------------
>
> Key: MULE-4104
> URL:
http://www.mulesource.org/jira/browse/MULE-4104> Project: Mule
> Issue Type: Bug
> Components: Core: Exception Handling
> Affects Versions: Bug Backlog (2.1.x, 2.2.x)
> Reporter: Ross Mason
> Assignee: Travis Carlson
> Priority: Critical
> Fix For: Bug Backlog (2.1.x, 2.2.x)
>
>
> Mule always returns a NullPayload regardless.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.mulesource.org/jira/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
