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

Sergey Beryozkin updated DOSGI-108:
-----------------------------------

    Fix Version/s:     (was: 1.3)
                   1.6.0

If the team agrees that the multiple values can not be supported then we'd need 
to report a service construction exception. If it is deemed that multiple 
values are to be supported then IMHO we should keep this extension (for the 
only case when a description is located in the resource file with no 
Spring/Blueprint involved), document it as such and recommend users to use 
other standards means of providing multiple values when possible 
                
> service.exported.interfaces doesn't support comma-seperated String value
> ------------------------------------------------------------------------
>
>                 Key: DOSGI-108
>                 URL: https://issues.apache.org/jira/browse/DOSGI-108
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Bert Jacobs
>            Assignee: Sergey Beryozkin
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> I've got a Declarative Service component which has more than one interface. I 
> declare the *service.exported.interfaces* property as "interface1,interface2" 
> and the default type String (I cannot specify String[] per the SCR spec).
> According to 
> http://cxf.apache.org/distributed-osgi-reference.html#DistributedOSGiReference-ServiceProviderpropertiesForConfiguringSOAPbasedservicesandconsumers
>  this String can be split on comma's.
> The service won't deploy because the *RemoteServiceAdminCore* class _doesn't_ 
> split this String and hence won't recognize the interfaces.
> Tested with 1.3-SNAPSHOT, built on 2012-01-23.

--
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

Reply via email to