We're using the event notification framework in Camel to perform logging of
certain route metrics based on ExchangeSentEvents. Generally this works just
fine as long as the route we are monitoring is part of a larger route where it
is being called via something like a to(). If the sub-route is u
I did find the problem and the solution.
The problem is that Camel always rolled back the file at the from SFTP URI
so the entire route is repeated indefinitely. There was no way (I could
find) to configure Camel to break out of this route with an exception when
the unmarshal bean threw an except
You cannot do that, but you can track the failures handled attribute
in JMX which we be incremented when you handle that exception.
On Mon, Nov 6, 2017 at 8:22 PM, David Hoffer wrote:
> I’m having trouble getting the exception behavior I’m looking for. What I
> expected this to do is when any e
If you use http/http4 components etc there is an option to turn of
throwing exception on error. See the documentation.
On Mon, Nov 6, 2017 at 11:24 PM, Rajpal Paryani wrote:
> Hi,
>
> We have recently switched to Apache Camel 2.18.4 in our web service
> from the older version 2.11.1. We use camel
Hi
No as the annotation requires a value and thus "" is like not in use.
We would need to add a new attribute required boolean true|false so
you can set it to required = false.
You are welcome to log a JIRA and work on a github PR if you fancy
On Tue, Nov 7, 2017 at 4:28 PM, Steve Huston wrote:
I am using Camel 2.19.1 and have a question on @PropertyInject with a default
value. I have the following:
public class MyStuff {
@PropertyInject(value="testVal", defaultValue="")
private String testVal;
...
}
When this class is instantiated and injected, if there is no 'testVal" in
pro
