Patch to apply TransformerTemplate to AxisServiceComponent result

• Includes test case?:

  yes
• User impact:

  Medium
• Similar Issues:

  None

I have a project that multicasts to axis endpoints. When I migrated from 2.1 to 2.2, the aggregator broke because the correlation properties were no longer being set on the response messages. A bit of digging traced the change in behaviour to revision 14035 (http://fisheye.codehaus.org/changelog/mule/?cs=14035).

I compared Axis component calls to CXF component calls and saw that the result of a CXF call is transformed by the AbstractComponent before it's returned to the CxfServiceComponent whereas the result of an Axis call is processed after AxisServiceComponent. By the time AbstractComponent's createResultMessage(..) is called on an Axis result, the result is a MuleMessage the TransformerTemplate isn't applied.

Given my limited experience with Mule, I saw two potential fixes:
1. Change the return value of AxisServiceComponent's onCall() to a non-MuleMessage type, or
2. Apply the TransformerTemplate to the message before it's returned from onCall()

I decided on the latter, since it seems less hacky though probably still a little naive. Attached is the patch to AxisServiceComponent and a test case to demonstrate the fix.