camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Babak Vahdat <babak.vah...@swissonline.ch>
Subject Re: camel-quickfix RequestReplyExample java.io.IOException
Date Sun, 16 Dec 2012 12:35:24 GMT
Hi

I logged a ticket to not forget about this bug:

https://issues.apache.org/jira/browse/CAMEL-5880

Babak


Babak Vahdat wrote
> Am 14.12.12 16:48 schrieb "lawkai" unter &lt;

> kai.law@

> &gt;:
> 
>>Hi Babak,
>>
>>I have checked the latest version in trunk.
>>
>>While I agree that the ExecutionReport did get printed out via the
>>additional route to the bean QuickfixjMessageJsonPrinter, wouldn't it be
>>better if it gets routed back to become the http response for the  request
>>(http://localhost:9123/order/status/?sessionID=FIX.4.2:TRADER->MARKET&orde
>>rID=abc)?
>>
> 
> No with the current camel-quickfix codebase this is currently not possible
> as
> QuickfixjEndpoint doesn't adhere the InOut MEP if you would ask for it
> through
> the option:
> 
>    exchangePattern=InOut
> 
> or the DSL element:
> 
>    setExchangePattern(ExchangePattern.InOut)
> 
> Because it always sticks to InOnly MEP (see QuickfixjEndpoint on trunk
> lines
> 93/94) so that you can't provide the ExecutionReport as the result of
> Routing
> Slip EIP usage, correspondingly as the HTTP response. BTW I'm not familiar
> with
> QuickFixJ or the FIX protocol at all but maybe there're others on the
> forum who
> knows how to achieve this.
> 
> Babak
> 
>>
>>
>>
>>--
>>View this message in context:
>>http://camel.465427.n5.nabble.com/camel-quickfix-RequestReplyExample-java-
>>io-IOException-tp5723769p5724106.html
>>Sent from the Camel - Users mailing list archive at Nabble.com.





--
View this message in context: http://camel.465427.n5.nabble.com/camel-quickfix-RequestReplyExample-java-io-IOException-tp5723769p5724165.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message