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

Henning Treu commented on FELIX-5506:
-------------------------------------

Is there a plan to apply this patch and release a new version of 
org.apache.felix.scr.ds-annotations? We now need to provide our own 
AnnotationProcessor to proceed with DS Annotations 1.3.

> OSGi's @Component parameter configurationPid is handled incorrectly
> -------------------------------------------------------------------
>
>                 Key: FELIX-5506
>                 URL: https://issues.apache.org/jira/browse/FELIX-5506
>             Project: Felix
>          Issue Type: Bug
>          Components: SCR Tooling
>    Affects Versions: scr generator 1.16.0
>            Reporter: Christian Luijten
>         Attachments: maven-scr-plugin-ds-annot-1.3.patch
>
>
> Given the following class:
> {code:java}
> package xxx;
> import org.osgi.service.component.annotations.Component;
> @Component(configurationPid = "GeneratorComponentPid")
> public class GeneratorComponent {
> }
> {code}
> When running it through the SCR Generator, it produces the following XML:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?><components 
> xmlns:scr="http://www.osgi.org/xmlns/scr/v1.2.0";>
>     <scr:component name="xxx.GeneratorComponent" 
> configuration-pid="[Ljava.lang.String;@76954a33">
>         <implementation class="xxx.GeneratorComponent"/>
>     </scr:component>
> </components>
> {code}
> I expected it to produce:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?><components 
> xmlns:scr="http://www.osgi.org/xmlns/scr/v1.2.0";>
>     <scr:component name="xxx.GeneratorComponent" 
> configuration-pid="GeneratorComponentPid">
>         <implementation class="xxx.GeneratorComponent"/>
>     </scr:component>
> </components>
> {code}
> {{org.osgi.service.component.annotations.Component}} and 
> {{org.apache.felix.scr.annotations.Component}} have different definitions for 
> {{configurationPid}}, which might explain this behavior.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to