<all> router incorrectly calls a jax-ws endpoint

• User impact:

  Medium
• Migration Impact:

  This used to work in 3.1.2
• Similar Issues:

  None

When using
<all>
...
<http:outbound-endpoint address="http://localhost:8081/united" exchange-pattern="request-response" >
<cxf:jaxws-client serviceClass="com.mulesoft.ticketing.TicketPriceService" operation="getPrice" />
</http:outbound-endpoint>

...
</all>

The service is called incorrectly and has XML errors in the SOAP envelope. However when you use a VM endpoint to call a flow with the exact same http:outbound-endpoint it works just fine

so the example would be

<all>
...
<vm:outbound-endpoint path="FrontierRequest" exchange-pattern="request-response" />

...
</all>

<flow name="xyzflow">
<vm:inbound-endpoint path="FrontierRequest" exchange-pattern="request-response" />
<http:outbound-endpoint address="http://localhost:8081/united" exchange-pattern="request-response" >
<cxf:jaxws-client serviceClass="com.mulesoft.ticketing.TicketPriceService" operation="getPrice" />
</http:outbound-endpoint>
</flow>

<flow name="unitedFlow">
<http:inbound-endpoint exchange-pattern="request-response"
address="http://localhost:8081/united" >
<cxf:jaxws-service serviceClass="com.mulesoft.ticketing.TicketPriceService" />
</http:inbound-endpoint>
<component class="com.mulesoft.ticketing.TicketPriceServiceImpl"></component>
<response>
<append-string-transformer message=" United"/>
</response>
</flow>