Hi Ralph, Whether the message is written to the wire as a FI or not is a functionality of the message formatter so disabling the FI to the backend endpoint and re-enabling the FI for the response to the client is theoretically possible with Synapse, but I have never tried this.
To try this out, configure the axis2.xml to enable the FI as described in this article [1] and then set the messageType property to application/soap+fastinfoset or application/fastinfoset as appropriately using the property mediator in the synapse configuration to enable FI and change the messageType propety to the relevant message type of the backend endpoint to disable FI for the backend requests. [1] - http://wso2.org/library/2686 Thanks, Ruwan On Mon, Nov 9, 2009 at 10:10 PM, <[email protected]> wrote: > Hi, > > I want to configure synapse as a FastInfoset-capable proxy for a number of > existing services. > Some of them are based on SOAP stacks other than Axis2 and do not have the > capability of FastInfoset. > > Is there an easy way to configure synapse in a way that proxy services can > be called using FastInfoset and endpoints get called using simple > soap/xml? > This should include the backward direction; meaning that non-FI responses > from the endpoints get translated into FI-responses to the client. > > Thank you. > > Greetings, Ralph. -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: [email protected]; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
