Hi Asankha, thanks for your replay, now I did to subscribe to the [email protected] list as you said. The callout mediator Sample 430 is not clear enough for me.. My requirements are: 1: synapse receive the SOAP request from a client which its web service destination To: ("http://localhost:8010/ProviderMessage";) 2: synapse call out External Web service To: ("http://localhost:8010/ExternalWS";) and the operation signature is (String Emulate(String s1,String s2)) 3: if the return value of the 2 is ="drop" then the SOAP request in 1 will be dropped 4: if the return value of the 2 is ="delay" then the SOAP request in 1 must be delayed for 3 seconds and then sent to its final web service destination To: ("http://localhost:8010/ProviderMessage";) 5: if the return value of the 2 is ="doNothing" then the SOAP request in 1 is sent to its final web service destination To: ("http://localhost:8010/ProviderMessage";) 3: if the return value of the 2 is ="Modify" then the SOAP request in 1 will be modified by a mediator (will be written latter) and then sent to its final web service destination To: ("http://localhost:8010/ProviderMessage";) I hope i managed to clarify my requirements Thanks for the help
Date: Tue, 22 Apr 2008 17:00:54 +0530From: [EMAIL PROTECTED]: [email protected]; [EMAIL PROTECTED]: Re: calling external ws from synapse ZarigFirst of all you need to subscribe to the [email protected] list before you can post messages and receive replies. I manually approved your mail through moderation, and copied this email to your private mailbox this time :-) this is synapse.xml: ... <syn:class name="samples.mediators.test1"/> <syn:send> ... this is my mediator: ... RPCServiceClient serviceClient = null;...The problem is that you are trying to use standard Axis2 to invoke the callout from within your mediator, and then trying to send.. and this probably conflicts with the axis2 configuration initialized by the Synapse environment already initiated by the way, i know callout mediator, however I think it can not satisfy my requirements. Why do you say that this does not satisfy your requirements? Can you elaborate your requirement a bit more.. The callout mediator performs a blocking send, while the send mediator will not block when using non-blocking transports such as the NIO based http/s.. These should allow you to do almost any scenario without writing your own mediator to do a callback.. you typically would want to write a new mediator to perform a custom transformation (e.g. proprietary data formats) etc and not for sending out..asankha _________________________________________________________________ Bag extra points with the Walkers Brit Trip Game http://www.walkersbrittrips.co.uk/game
