[ 
https://issues.apache.org/jira/browse/CAMEL-10169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387868#comment-15387868
 ] 

ASF GitHub Bot commented on CAMEL-10169:
----------------------------------------

GitHub user borcsokj opened a pull request:

    https://github.com/apache/camel/pull/1083

    CAMEL-10169: support service lookup by service.pid in OSGi environment

    Created patch to support service lookup by service.pid in OSGi environment

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/borcsokj/camel feature/CAMEL-10169

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1083.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1083
    
----
commit b57af73ae42b3f4251d065e00f9fb0887409c34f
Author: Börcsök József <[email protected]>
Date:   2016-07-21T15:07:13Z

    CAMEL-10169: support service lookup by service.pid in OSGi environment

----


> supporting OSGi service.pid by registry
> ---------------------------------------
>
>                 Key: CAMEL-10169
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10169
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-osgi
>            Reporter: Börcsök József
>            Priority: Minor
>             Fix For: 2.18.0
>
>
> Declarative services are registered for interfaces only by default in OSGi 
> environment. Components that implement Processor interface only (i.e. name of 
> the class is not specified in Service annotation) cannot be added as "bean:" 
> (components) in Camel routes.
> LookupByName method in default OsgiServiceRegistry should be extended to 
> support service.pid that references the exact component class so existing 
> services could be used in routed without source changes/redundant source 
> fragments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to