My routes use a bean for utility functions...
public void setSerializationType(Exchange ex, Class clazz) { ... }
I've tried calling the method using Simple expressions, but Camel always
complains it's unable to bind the Class parameter; is this even possible?
Based on documentation, Stri
Good idea.
And don't forget to file a JIRA first:
https://issues.apache.org/jira/browse/CAMEL
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.co
Well done!
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Fri, Apr 1, 2016 at 3:58 PM, Bilgin Ibryam w
One thing you might consider is to use a DTO or "shopping cart" as the body
of your messages to store the state and not use the Exchange itself.
I'm fairly certain Claus isn't at odds with your impulse to use beans
independent of Camel as I think he even writes about that in his book. So
at the
You can also throw an exception in a processor to short circuit. From the
use case it does sound like a runtime exception of some sort.
Part of the answer to that question depends on why the processors want to
short circuit. Can you put a validator at the beginning of the route? If
the condit
Since you’re processing with beans, maybe you could combine the process and
filter steps to make your routes a little more concise?
You may have some pretty deeply nested XML, but it’s a little better
In that case you can also try the interceptor.
Something like this, note the stop() at the end.
intercept().when(header("ROUTE_STOP").isNotNull()).stop();
Cheers,
Taariq
On Sun, Apr 3, 2016 at 5:01 AM, bocamel wrote:
> Quinn,
>
>
>
> Thanks for the response. I think filter would be the clos
