Yup, its "method" instead of "methodName". I stared at it for a long while
and still missed the renaming the bean parameters:)
praveen.sharma wrote:
>
> There is something amiss in using Camel 2.0.0 with bean binding. Again,
> the example shown below was working with 1.6.1 Camel version, but Camel
> 2.0.0 or 2.0-M3 gives following error
>
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: bean://QoSMonitorS?methodName=monitorImage due to: There
> are 1 parameters that couldn't be set on the endpoint. Check the uri if
> the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[{methodName=monitorImage}]
> at
> org.apache.camel.impl.DefaultComponent.validateParameters(DefaultComponent.java:115)
> at
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:93)
> at
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:394)
> ... 40 more
>
> Camel route defined as
> ...
> to ("bean:QoSMonitorL?methodName=monitorImage")
>
>
> Bean is defined as
>
> @Handler
> public void monitorImage(@Body final Exchange exch) {
> ...
> }
>
--
View this message in context:
http://www.nabble.com/Camel-2.0.0-and-bean-binding-tp25877580p25879298.html
Sent from the Camel - Users mailing list archive at Nabble.com.
