Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I think there are two elegant way to do that (excluding the one that involves changing the webservice interface)</p> <p>Store the request into a session variable and restore it afterwards. Here is how your flow would look like:</p> <pre><code>&lt;flow name="testService"&gt; &lt;http:inbound-endpoint address="http://localhost:62005/test" exchange-pattern="request-response"&gt; &lt;cxf:jaxws-service serviceClass="com.test.ServicePortType" /&gt; &lt;/http:inbound-endpoint&gt; &lt;message-properties-transformer scope="session"&gt; &lt;add-message-property value="payload" key="originalPayload" /&gt; &lt;/message-properties-transformer&gt; &lt;component class="com.test.ServiceImpl" /&gt; &lt;/flow&gt; </code></pre> <p>Use the enricher around the component to store the returned value into a variable so that it won't become the payload of your flow. Following an example of how to achieve this</p> <pre><code>&lt;flow name="Echo" doc:name="Echo"&gt; &lt;http:inbound-endpoint exchange-pattern="request-response" host="localhost" port="6090" path="echo" encoding="UTF-8" /&gt; &lt;cxf:jaxws-service serviceClass="org.mule.example.echo.Echo" /&gt; &lt;enricher target="#[variable:echo]"&gt; &lt;component class="org.mule.example.echo.Echo" /&gt; &lt;/enricher&gt; &lt;logger level="ERROR" message="#[variable:echo]"/&gt; &lt;/flow&gt; </code></pre> <p>You can find more informations on the enricher <a href="http://www.mulesoft.org/documentation-3.2/display/MULE3USER/Message+Enricher" rel="nofollow">here</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload