Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.9.2, 2.10.0
-
None
-
DefaultCamelBeanPostProcessor will try to set the CamelContext property when the bean is instance of CamelContextAware. It will mass up the CamelContext setting when the bean has the property of CamelContextId and there are more than one CamelContext in the Application Context. So We just need to make sure the CamelContextId take effect even the CamelContext is already set to the bean to fix this kind of issue.
DefaultCamelBeanPostProcessor will try to set the CamelContext property when the bean is instance of CamelContextAware. It will mass up the CamelContext setting when the bean has the property of CamelContextId and there are more than one CamelContext in the Application Context. So We just need to make sure the CamelContextId take effect even the CamelContext is already set to the bean to fix this kind of issue.
-
Unknown