You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2017/03/13 08:28:04 UTC

[jira] [Closed] (FELIX-5424) Augment exported service metadata

     [ https://issues.apache.org/jira/browse/FELIX-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert closed FELIX-5424.
---------------------------------

> Augment exported service metadata
> ---------------------------------
>
>                 Key: FELIX-5424
>                 URL: https://issues.apache.org/jira/browse/FELIX-5424
>             Project: Felix
>          Issue Type: Improvement
>          Components: Maven Bundle Plugin
>            Reporter: Paolo Antinori
>            Assignee: Guillaume Nodet
>             Fix For: maven-bundle-plugin-3.3.0
>
>
> When Apache Aries Blueprint installs a service that points to a {{[bean]}} node that has its {{id}} attribute specified, it adds an additional metadata entry to the service registry:
> {code}
> osgi.service.blueprint.compname = myBeanId
> {code}
> That information is not automatically added to the Headers section of a generated bundle though, thus preventing some kind of validation offline.
> The proposed patch adds the additional metadata at build time.
> This is a snippet of a use case that requires this:
> {code:xml}
>   <bean id="mysql-ds" class="com.mysql.jdbc.jdbc2.optional.MysqlXADataSource">
>   </bean> 
>   
> <service id="sqlDataSourceExporter" ref="mysql-ds" interface="javax.sql.DataSource">
> </service>
>   
> {code}
> And, in another file:
> {code:xml}
>     <reference id="mysql-db" interface="javax.sql.DataSource" availability="mandatory" component-name="mysql-ds" />
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)