You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Samrat Dhillon (Jira)" <ji...@apache.org> on 2021/06/18 12:35:00 UTC
[jira] [Created] (CAMEL-16733) Calling bean method by type results
in creation of new bean rather using an existing one from the registry
Samrat Dhillon created CAMEL-16733:
--------------------------------------
Summary: Calling bean method by type results in creation of new bean rather using an existing one from the registry
Key: CAMEL-16733
URL: https://issues.apache.org/jira/browse/CAMEL-16733
Project: Camel
Issue Type: Bug
Components: camel-bean
Affects Versions: 3.10.0
Reporter: Samrat Dhillon
The below code results in creation of a new bean of type MyBean rather than looking up an existing instance from the registry. Also there is an imposition that MyBean has a no-args ctor for camel to construct a new bean. This behaviour is very confusing when an existing bean can be found from the registry such as spring which can use ctor injection without having the need for a default ctor
public void configure() throws Exception {
from("direct:a").transform().method(MyBean.class).to("mock:a");
from("direct:b").transform().method(MyBean.class).to("mock:b");
}
};
--
This message was sent by Atlassian Jira
(v8.3.4#803005)