Hey Guys,

I am just wondering what your best practices are. Despite the marvelous job
in "Apache Camel Developer's
Cookbook<http://www.amazon.com/dp/1782170308/ref=rdr_ext_tmb>",
and in http://camel.apache.org/cookbook.html, there are still things that
one comes up with that simplify one's life with Camel.

Here are two of mine:

1) This one is implicit when you look at Camel source: always prefix your
camel component header's name with Camel+ComponentName. For instance,
CamelAzurePreset. This has helped me during troubleshooting and when one
needs to clear the headers for a given component. One can use a matching
pattern to identify all headers pertaining to a component.

2) When creating a component, do not pass stuff through the body of the
message. Preferably, use only headers/properties. When using the body,
people have to do a lot of extra work to call your component: backup their
body, put the parameter you need in the header, call your component,
restore the original body.

Do these make sense to you? What other best practices do simplify your
daily Camel ride?

Thanks for sharing.

Max.

Reply via email to