[
https://issues.apache.org/jira/browse/CAMEL-10135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369282#comment-15369282
]
Arno Noordover commented on CAMEL-10135:
----------------------------------------
It doesn't seem to be a bug.
The creation of the bean is done by org.apache.camel.model.BeanDefinition and
begins by getting the clazz on line 274.
Eventually the line 304 is executed
{code}
// this is only for invoking static methods on the bean
beanHolder = new ConstantStaticTypeBeanHolder(clazz,
routeContext.getCamelContext());
{code}
My conclusion is that no instance is created because the processor is going to
try and call static methods on your bean-class.
When you add the following method to your bean
{code}
public static String doSomeBrickletThing(String hello) {
return "Camel in your house!";
}
{code}
you don't see any failure.
> Bean creation exception swallowed
> ---------------------------------
>
> Key: CAMEL-10135
> URL: https://issues.apache.org/jira/browse/CAMEL-10135
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.15.1
> Environment: Any
> Reporter: Geert Schuring
> Labels: beaninvocation, camel, constructor, exception-handling
> Attachments: FilterTest.java
>
>
> When a Route is referring to a Java Bean by class type while that class has
> no default constructor, Camel should throw an exception indicating that
> creation of the bean failed. Instead it ignores this problem resulting in an
> exchange encountering a null pointer exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
