[
https://issues.apache.org/jira/browse/DOSGI-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681058#comment-13681058
]
Sergey Beryozkin commented on DOSGI-108:
----------------------------------------
I'd prefer to keep the option of having a comma-separated value supported and
document that this option may not be portable. That said, David documented
originally it is possible for it to have comma separated values, users have
read into it, and IMHO it just has to be maintained
> 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.3
>
>
> 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
