Peter Palaga created CAMEL-21977:
------------------------------------
Summary: Remove CamelBeanMethodName constants
Key: CAMEL-21977
URL: https://issues.apache.org/jira/browse/CAMEL-21977
Project: Camel
Issue Type: Task
Reporter: Peter Palaga
The commit
https://github.com/apache/camel/commit/cbd1972c3f908101cb63edca677f19c19b029316
solving https://issues.apache.org/jira/browse/CAMEL-21851
Has effectively removed support for selecting the bean method through a header.
It is also properly stated in the migration guide for Camel 4.10.2:
https://camel.apache.org/manual/camel-4x-upgrade-guide-4_10.html#_camel_bean
To make end users better aware of that fact, we should remove all constants
storing the {{CamelBeanMethodName}} string. Deprecating is no enough. Failing
at build time is mauch better for the users. Those are:
* org.apache.camel.Exchange.BEAN_METHOD_NAME
* org.apache.camel.component.bean.BeanConstants.BEAN_METHOD_NAME
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
