concept bean method in category camel

This is an excerpt from Manning's book Camel in Action.
First you create an instance of
SimpleRegistryand populate it withHelloBeanunder thehelloBeanname 1. Then, to use this registry with Camel, you pass the registry as a parameter to theDefaultCamelContextconstructor 2. To aid when testing, you createProducerTemplate, which makes it simple to send messages to Camel, as you can see in the test method. Finally, when the test is done, you clean up the resources by stoppingProducerTemplateand Camel 3. In the route, you use thebeanmethod to invokeHelloBeanby thehelloBeanname you gave it when it was enlisted in the registry 1.

This is an excerpt from Manning's book Camel in Action.
When the compiler compiles this code, it can’t see that you want to invoke the echo method on the EchoBean. From the compiler’s point of view, EchoBean.class and "echo" are parameters to the bean method. All the compiler can check is that the EchoBean class exists; if you had misspelled the method name, perhaps typing "ekko", the compiler could not catch this mistake. The mistake would end up being caught at runtime, when the BeanProcessor would throw a MethodNotFoundException stating that the method named ekko does not exists.