On Mon, Sep 14, 2009 at 5:51 AM, jamhit hitha.a...@sabre-holdings.com wrote:
Thanks Claus. I am not sure, if the issue is due to remote host forcibly
closing connection. My simple java socket client works fine by sending
multiple concurrent transactions to the same legacy server. I have a
Hi,
Yes, you can use mock endpoint to check the exchange.
According to you description of the production configuration,
I think you can add a mock endpoint at the end of route, and check the
exchange which is routed to this endpoint. But this will change your
production route rule a litter
2009/9/14 Scott Parkerson scott.parker...@ateb.com:
Hello,
I'm trying to use Camel 1.6.1 in SMX 4.1.0.2 (FUSE) and the POJO
Producing / Consuming annotations as described in the online
documentation.
In one class (a CXF-based RESTful webservice), I have the following set
up:
//
On Mon, 2009-09-14 at 16:07 +0100, James Strachan wrote:
Are you creating your OutboundFooRequestHandlerImpl class by
configuring it in Spring XML? Or are you using the Spring 3 component
scan stuff?
Well, that question made me realize that I need to instantiate the bean
via Spring. Turns out
Hello,
I'm trying to use Camel 1.6.1 in SMX 4.1.0.2 (FUSE) and the POJO
Producing / Consuming annotations as described in the online
documentation.
In one class (a CXF-based RESTful webservice), I have the following set
up:
// OutboundFooRequestHandler is an interface (see below)
This simple example will fail in http component with I/O Exception.
Worked in 2.0-M3 but fails in 2.0.0
Namespaces ns = new Namespaces(atom, http://www.w3.org/2005/Atom;);
from(rss:http://www.plosone.org/article/feed;)
.marshal().rss()