cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Commented: (CXF-1145) Not able to set the namespace for a service wsdl
Date Fri, 02 Nov 2007 15:37:50 GMT


Daniel Kulp commented on CXF-1145:

Testcase added.    In your spring config:

  <simple:server address="/serviceWithCustomNS"
       <bean class="org.apache.cxf.aegis.databinding.AegisDatabinding" />
      <bean class="org.apache.cxf.authservice.AuthServiceImpl" />
    	<bean class="org.apache.cxf.service.factory.ReflectionServiceFactoryBean">
    		<property name="serviceConfigurations">
    				<bean class="org.apache.cxf.aegis.databinding.AegisServiceConfiguration">
    					<property name="serviceNamespace" value=""/>
    				<bean class="org.apache.cxf.service.factory.DefaultServiceConfiguration"/>

I just deployed new snapshots that should have this in it.

> Not able to set the namespace for a service wsdl
> ------------------------------------------------
>                 Key: CXF-1145
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Tawfik Lachheb
>            Priority: Critical
>             Fix For: 2.0.3
> We are trying to upgrade our published services from xfire to cxf using the simple frontend
with aegis.  When we set the namespace for classes in the service's object model the namespaces
appear ok.  The problem is that the namespace of the service class is auto-generated and becasue
it does not match what we set for the object model, it causes issues with some client SOAP
> In xfire, we used to be able to set the service namespace by doing something like this:
>     <bean id="..." class="org.codehaus.xfire.spring.remoting.XFireExporter">
>         <property name="namespace" ref="nameSpace"/>
>         ...
>     </bean>
> This capability does not seem to be available in cxf.
> We have tried setting the namespace in the service aegis file with no success.
> Thanks

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message