CompositeOperationTransformer.CompositeResultTransformer works by analyzing the "step-x" entries in the remote response's "result" node, and then transforming that node.

This breaks down when the failure actually occurs in the remote CompositeOperationHandler, as will be the case if the step refers to a resource or operation that is undefined on that node. In that case there is no "result" node with steps, just a top level failure.

CompositeResultTransformer will actually add a "result" node with the expected error message in this case, but that basically works by luck. And the high level error message for the overall op will no be transformed.

Possible improvements:

1) CompositeOperationHandler sets up a result node in this case, so CompositeResultTransformer can process it.

2) CompositeResultTransformer can try and fix up the top level error message as well.