4. Beans | Mastering Apache Camel

Bean and method bindings

During step 2, when the BeanProcessor selects the method to invoke, the message/method bindings can occur in different ways. Camel tries the following steps to resolve the bean method:

If the incoming message (in message) contains the CamelBeanMethodName header, then this method is invoked, converting the in message body to the type of the method's argument.
You can specify the method name directly in the route definition (on the bean endpoint).
If the bean contains a method annotated with @Handler, then this method is invoked.
If the bean can be converted to a processor (containing the process() method), we fall back to the regular processor usage as seen in the previous chapter.
If the body of the in message can be converted to a org.apache.camel.component.bean.BeanInvocation component, then it's the result of the getMethod() method, which is used as the method name.
Otherwise, the body type of the in message is used to find a matching method.

Several exceptions can occur...

Tech Concepts

Programming languages

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Mastering Apache Camel

By : Jean-Baptiste Onofré

Mastering Apache Camel

By: Jean-Baptiste Onofré

Overview of this book

Bean and method bindings

Mastering Apache Camel

By : Jean-Baptiste Onofré

Mastering Apache Camel

By: Jean-Baptiste Onofré

Overview of this book

Bean and method bindings

Confirmation

Buy this book with your credits?

Submit Your Feedback

Create a Free Account To Continue Reading

Sign in to activate your 7-day free access