Charith Wickramarachchi wrote:
>
> One thing you can do is use the Clone Mediator. Where in one clone target
> you can just send it through and in another target one you can do the xslt
> and log and then drop the message.
>
Thanks Charith, clone seems to be the way to go, however
as I said I am a rookie with Synapse and I don't see an actual example of
how I setup clone.
The only thing I did before was a simple filter, which is the bases for what
I need to do again.
My typical application is to use Synapse as a Soap Intermediary. We have a
machine with
VPN access to a 3rd party WS. I run my code on a box that has access to our
VPN box. I point
my TargetEndpoint URLs to the Synapse Running on our VPN Box and it
Filters/Forwards the
Soap between my box and the outside WS.
I have used the following in the past:
<sequence name="main">
<!-- log all attributes of messages passing through -->
<log level="full"/>
<!-- filtering of messages with XPath and regex matches -->
<filter source="get-property('To')" regex=".*/Something.*">
<then>
<send>
<endpoint>
<address
uri="http://SoapWS_IP_ADDR:PORT/stuff/services/Somthing"/>
</endpoint>
</send>
<drop/>
</then>
</filter>
<send/>
</sequence>
</definitions>
How do I combine this filter/forwarding with Clone?
thanks
--
View this message in context:
http://old.nabble.com/Howto-run-XSLT-Transform-on-logged-Soap-Msgs-tp31372526p31443731.html
Sent from the Synapse - User mailing list archive at Nabble.com.
