cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Jacobs (JIRA)" <>
Subject [jira] [Commented] (DOSGI-108) service.exported.interfaces doesn't support comma-seperated String value
Date Thu, 20 Jun 2013 15:23:20 GMT


Bert Jacobs commented on DOSGI-108:

I'm the reporter of this bug, and as it turns out I never used it with comma's. Sorry for
I think I was simply confused back at the time because the documentation said it could contain
comma-seperated values and I logged this after being frustrated that my services wouldn't
expose themselves.

Now I guess I should check this, but I believe the reason I didn't use it is because CXF DOSGi
doesn't document how those different services can be exported as different endpoints. The
first interface likely deploys, but the other interfaces will trigger an "already bound to
address xxxx" error as they use the same service properties (because it's the same service

At any rate, it's been a while I touched any of this. My services worked at one point and
I simply didn't touch them again out of fear of breaking them.
> service.exported.interfaces doesn't support comma-seperated String value
> ------------------------------------------------------------------------
>                 Key: DOSGI-108
>                 URL:
>             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
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:

View raw message