[
https://issues.apache.org/jira/browse/DOSGI-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690192#comment-13690192
]
Sergey Beryozkin edited comment on DOSGI-194 at 6/21/13 10:56 AM:
------------------------------------------------------------------
Hi, can such a registration be covered by a single endpoint ? I reckon a JAX-RS
endpoint may cover multiple interfaces (a service bean per every interface, all
within a single endpoint), but what about WS - I guess we can get an internal
composite interface auto-generated and have a single endpoint ?
was (Author: sergey_beryozkin):
Hi, can such a registration be covered by a single endpoint ? I reckon a
JAX-RS endpoint may cover multiple interfaces (a service bean per every
interface, all withing a single endpoint), but what about WS - I guess we can
get an internal composite interface auto-generated and have a single endpoint ?
> Decide how DOSGi needs to handle service.exported.interfaces with multiple
> values
> ----------------------------------------------------------------------------------
>
> Key: DOSGI-194
> URL: https://issues.apache.org/jira/browse/DOSGI-194
> Project: CXF Distributed OSGi
> Issue Type: Task
> Components: DSW
> Reporter: Sergey Beryozkin
> Fix For: 1.6.0
>
>
> According to the original DOSGi CXF documentation
> "service.exported.interfaces" may have multiple values.
> The multiple values can be specified as a String array with Declarative
> Services or by a having a property value containing a comma-separated list of
> strings.
> The purpose of this task is to decide how DOSGI should handle this property
> when it has multiple String values. If the decision is made that no multiple
> values are supported then DOSGI will need to report a service exception when
> the property contains multiple values, irrespectively of how these multiple
> values have been specified (via Declarative Services or CXF specific
> extension)
--
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
