Help in understanding route behaviour

[abaldoni <al...@comune.faenza.ra.it>]

Hello, I'm new to Camel and I'm starting to learn it.
I have a problem with the following route: 
	from()   
		.unmarshal()     
			.filter().javaScript()    
				.setHeader()           
				.convertBodyTo()   
				.to();

When I run it, the filter() gets applied; if filter() returns true,
everything is ok; if filter() returns false, the setHeader() and convertTo()
steps are bypassed but the to() step is not.

I'm using Camel 2.11.1 in a Java SE application.

Regards,
Alessandro



--
View this message in context: http://camel.465427.n5.nabble.com/Help-in-understanding-route-behaviour-tp5738936.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Help in understanding route behaviour

[abaldoni <al...@comune.faenza.ra.it>]

The problem was with the from() producer. After enabling all the tracing
options as in http://camel.apache.org/tracer.html, I was able to understand
what was going on.

The actual code for the producer is:

    from("mina2:udp://<ip address>:514")

Somehow, with both mina and mina2, the source message is "echoed" back
between a random port and port 514.

Using Netty everything works as expected.




--
View this message in context: http://camel.465427.n5.nabble.com/Help-in-understanding-route-behaviour-tp5738936p5738988.html
Sent from the Camel - Users mailing list archive at Nabble.com.