Details
-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.20.0
-
Component/s: camel-core
-
Labels:None
-
Estimated Complexity:Unknown
Description
When calling a bean from a Camel route we can optimise to let BeanProcessor be used in a lighter-way without being a service as we dont need to keep its state, as its a one-time use object only being used to invoke the bean and discarded afterwards.
Where as a service is more intended for long time lifecycle which has state to start/stop etc.
