The parameter 'response-body-as' should be moved at the transformation level, as the attribute 'process-http-response-as'of 'out' and 'otherwise-out':
<rest:on-http-status code="200">
   <rest:out order-id="0" process-http-response-as="xml|json|auto|attachment">
      <rest:condition />
      <rest:transformation>
         <rest:xsl>200-consulter.xsl</rest:xsl>
      </rest:transformation>
   </rest:out>
   <rest:otherwise-out>
      <rest:transformation>
         <rest:xsl>200-consulter-default.xsl</rest:xsl>
      </rest:transformation>
   </rest:otherwise-out>
</rest:on-http-status>
 So, we can manage use cases where the HTTP body content has different nature (XML, JSON, binary) according to HTTP status and other criteria.
 
The parameter 'response-body-as' should be moved at the transformation level, as the attribute 'process-http-response-as'of 'out' and 'otherwise-out':
So, we can manage use cases where the HTTP body content has different nature (XML, JSON, binary) according to HTTP status and other criteria.