Hi Bill, On Thu, Jul 16, 2009 at 2:40 AM, PrgTrdr <[email protected]> wrote:
> > I have cloned Sample 259 to implement a use case where a FIX client > communicates with a Web Service. The system is working well as far as 1) > establishing the FIX session from the client to Synapse, 2) Logon, > 3)Sending > a New Order message, 4)performing an XSLT to create a WS request, 5)sending > the Request to the WS, 6)receiving back a Response from the WS, > 7)performing > an XSLT to convert the SOAP response to an XML-encapsulated FIX message. > But then the response message never flows back to the FIX transport (I can > tell by examining the QuickFIX/J logs). > > I am receiving (and converting) the WS Response message in a standard > "<out>" sequence. At the end I placed > > <send> > <endpoint key="FIXProxy"/> > </send> > > to see if that would make it work, but the message doesn't go out to FIX, > nor does it show up in the FIXProxy <outSequence> (I put some log mediators > in there to trace activity). > > Sample 259 is one-way only (FIX->SOAP). Can someone give me an idea about > what needs to be done to make this two-way? Perhaps changes to the > FIXProxy > configuration? How about placing an empty <send/> element in the <outSequence> of your proxy service? I think that should do the trick. Anyway please send in your full Synapse configuration for us to get a clear idea of the scenario. Thanks, Hiranya > > Thanks, > Bill > -- > View this message in context: > http://www.nabble.com/HTTP--%3E-FIX-Response-Handling-tp24505424p24505424.html > Sent from the Synapse - User mailing list archive at Nabble.com. > > -- Hiranya Jayathilaka Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
