cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Created] (DOSGI-145) Multiple services using HTTP Service and published from the same bundle do not work
Date Mon, 19 Nov 2012 11:56:59 GMT
Sergey Beryozkin created DOSGI-145:

             Summary: Multiple services using HTTP Service and published from the same bundle
do not work 
                 Key: DOSGI-145
             Project: CXF Distributed OSGi
          Issue Type: Bug
          Components: DSW
            Reporter: Sergey Beryozkin
             Fix For: 1.4

This issue was reported at the CXF users list and now is reproducible on the trunk.

Consider the following activator code:
public class Activator implements BundleActivator {
    private ServiceRegistration registration;
    private ServiceRegistration registration2;

    public void start(BundleContext bc) throws Exception {
        Dictionary props = getProperties("/greeter");
        registration = bc.registerService(GreeterService.class.getName(), 
                                          new GreeterServiceImpl(), props);
        props = getProperties("/greeter2");
        registration2 = bc.registerService(GreeterService2.class.getName(), 
                                          new GreeterServiceImpl2(), props);

    private Dictionary getProperties(String address) { 
    	Dictionary props = new Hashtable();

        props.put("service.exported.interfaces", "*");
        props.put("service.exported.configs", "");
        props.put("service.exported.intents", "HTTP");
        props.put("", address);
        return props;
    public void stop(BundleContext bc) throws Exception {


This is RS activator code but the issue will show itself for WS endpoints too.

After the deployment, requesting a service at "/greeter" will make "/greeter2" endpoint not
accessible and the other way around.

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