[
https://issues.apache.org/jira/browse/CAMEL-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594845#comment-13594845
]
Aaron Whiteside commented on CAMEL-6130:
----------------------------------------
Ah OK, So I still see a potential problem with that..
Service property's have no unique constraint in OSGi, so there could be a a
hundred services registered with the property name=hello, of all different
types. So we would have to iterate through the list trying to inject each one
until one fits? If you're OK with that approach I could implement it. Though I
would be worried at the number of services it would find... potential
performance issue.
> EndpointHelper.setReferenceProperties() does not work with OSGiServiceRegistry
> ------------------------------------------------------------------------------
>
> Key: CAMEL-6130
> URL: https://issues.apache.org/jira/browse/CAMEL-6130
> Project: Camel
> Issue Type: Bug
> Components: osgi
> Affects Versions: 2.9.5, 2.10.4
> Reporter: Aaron Whiteside
> Priority: Critical
> Fix For: 2.9.7, 2.10.5, 2.11.0
>
> Attachments: CAMEL-6130.patch
>
>
> EndpointHelper.setReferenceProperties() does not work with OSGiServiceRegistry
> setReferenceProperties() is hard-coded to lookup services of type
> Object.class.
> It should use reflection to determine the type that the setter method accepts
> and then use that type to lookup the reference in the service registry.
> At the moment this issue is stopping #bean references in Endpoints from being
> resolved when using an OSGiServiceRegistry, in OSGi you need to know the
> class of the service you want before hand.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
