Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the early version of the new website
https://camel.apache.org/staging/
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.
AOPAvailable as of Camel 2.0 @deprecated The AOP has been marked as Camel has a AOP concept in the DSL allowing you do do some custom before and/or after processing when routing an Exchange. This new AOP can span multiple processors (nodes in the route graph) and it uses endpoint URIs to allow invoking any kind of Camel component. The AOP supports the following callbacks in which you can use 1..n free of choice:
The difference between Using from Java DSLIn this route we want to use the AOP to do a before and after logging. from("jms:queue:inbox") .aop().around("log:before", "log:after") .to("bean:order?method=validate") .to("bean:order?method=handle") .end() .to("jms:queue:order"); Notice that we use the The aop in Java DSL have the following methods:
Using from Spring DSLIn Spring DSL its nearly the same as in the Java DSL however a bit differently <route> <from uri="jms:queue:inbox"/> <aop beforeUri="log:before" afterUri="log:after"> <to uri="bean:order?method=validate"/> <to uri="bean:order?method=handle"/> </aop> <to uri="jms:queue:order"/> Notice we use attributes on the <aop> tag to chose with AOP concept to use. At runtime that resolves into this messages flow: inbox -> log:before -> bean.validate -> bean.handle -> log:after -> order The aop in Spring DSL have the following attributes:
So in order to do an around we use both the See Also |