[ 
https://issues.apache.org/jira/browse/CXF-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539587
 ] 

Daniel Kulp commented on CXF-1145:
----------------------------------


I started on a way to make it work last night.  It's not quite as "simple", but 
it hopefully will work (although I haven't had time to write a testcase for it 
yet).  

Basically, if you create a ReflectionServiceFactoryBean, you can set the list 
of serviceConfigurations on it.   The DefaultServiceConfiguration object now 
has a serviceNamespace property that can be set.   

> Not able to set the namespace for a service wsdl
> ------------------------------------------------
>
>                 Key: CXF-1145
>                 URL: https://issues.apache.org/jira/browse/CXF-1145
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Tawfik Lachheb
>            Priority: Critical
>
> 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 toolkits.
> 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.

Reply via email to