You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2012/10/22 13:10:12 UTC

[jira] [Created] (DOSGI-126) Allow to use the servlet transport with automatic discovery

Christian Schneider created DOSGI-126:
-----------------------------------------

             Summary: Allow to use the servlet transport with automatic discovery
                 Key: DOSGI-126
                 URL: https://issues.apache.org/jira/browse/DOSGI-126
             Project: CXF Distributed OSGi
          Issue Type: Improvement
          Components: Discovery
    Affects Versions: 1.3.1
            Reporter: Christian Schneider
            Assignee: Christian Schneider
             Fix For: 1.4


Currently you can use org.apache.cxf.ws.address = /MyService already.
This specifies that you want to use the servlet transport.
The complete uri would then be : http://servername:port/cxf/MyService
Where "cxf" is symbolic for where the servlet transport registers itself.

The problem is that we send the /MyService address to zookeeper which results in a strange entry with -1 as port. Of course this address is then quite useless for other containers. 

So I think what we could do is define a variable in the config admin pid cxf-dsw:
servletPrefix: http://myserver:8080/cxf

This could then be prepended to any servlet address we find. So zookeeper will be happy. 


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

[jira] [Resolved] (DOSGI-126) Allow to use the servlet transport with automatic discovery

Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DOSGI-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider resolved DOSGI-126.
---------------------------------------

    Resolution: Fixed

1414835 28.11.2012 18:38:16, by cschneider
DOSGI-127 DOSGI-126 Use relative default address to create service endpoints but publish an absolute address for discovery
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/Activator.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/Constants.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/handlers/AbstractConfigurationHandler.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/handlers/AbstractPojoConfigurationTypeHandler.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/handlers/ConfigTypeHandlerFactory.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/handlers/LocalHostUtil.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/qos/IntentUtils.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/service/RemoteServiceAdminCore.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/test/java/org/apache/cxf/dosgi/dsw/handlers/ConfigTypeHandlerFactoryTest.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/test/java/org/apache/cxf/dosgi/dsw/handlers/PojoConfigurationTypeHandlerTest.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/test/java/org/apache/cxf/dosgi/dsw/qos/IntentManagerImplTest.java
M /cxf/dosgi/trunk/dsw/cxf-dsw/src/test/java/org/apache/cxf/dosgi/dsw/service/RemoteServiceAdminCoreTest.java 
                
> Allow to use the servlet transport with automatic discovery
> -----------------------------------------------------------
>
>                 Key: DOSGI-126
>                 URL: https://issues.apache.org/jira/browse/DOSGI-126
>             Project: CXF Distributed OSGi
>          Issue Type: Improvement
>          Components: Discovery
>    Affects Versions: 1.3.1
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 1.4
>
>
> Currently you can use org.apache.cxf.ws.address = /MyService already.
> This specifies that you want to use the servlet transport.
> The complete uri would then be : http://servername:port/cxf/MyService
> Where "cxf" is symbolic for where the servlet transport registers itself.
> The problem is that we send the /MyService address to zookeeper which results in a strange entry with -1 as port. Of course this address is then quite useless for other containers. 
> So I think what we could do is define a variable in the config admin pid cxf-dsw:
> servletPrefix: http://myserver:8080/cxf
> This could then be prepended to any servlet address we find. So zookeeper will be happy. 

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