[jira] [Commented] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541283#comment-17541283 ] Jean-Baptiste Onofré commented on CAMEL-15288: -- Yes, I think it's OK now. I close this Jira for now, let's reopen it if we need some updates. > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541278#comment-17541278 ] Martin Lichtin commented on CAMEL-15288: The behavior in 3.14 has changed and this may no longer be relevant.. > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527449#comment-17527449 ] Jean-Baptiste Onofré commented on CAMEL-15288: -- [~lichtin] yes, definitely. My bad, I have to switch back to Camel work. I will move forward asap. I will keep you posted. > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-15288) Camel OSGi: Allow for defining the Bean resolution order
[ https://issues.apache.org/jira/browse/CAMEL-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527436#comment-17527436 ] Martin Lichtin commented on CAMEL-15288: Can this one be considered at some point? It is a performance hit to constantly lookup OSGi services. > Camel OSGi: Allow for defining the Bean resolution order > > > Key: CAMEL-15288 > URL: https://issues.apache.org/jira/browse/CAMEL-15288 > Project: Camel > Issue Type: Improvement > Components: camel-osgi >Affects Versions: 2.24.3 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Major > > Currently OsgiDefaultCamelContext updates the registry and inserts > OsgiServiceRegistry as the _first_ registry into the list. > This can lead to undesirable behaviour, so an option to define the resolution > order will be helpful. > For example, it can be more appropriate to lookup local beans first, only go > to lookup an OSGi service if no local bean is found. Or it could be desired > to not lookup OSGi services at all. -- This message was sent by Atlassian Jira (v8.20.7#820007)
