cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tawfik Lachheb (JIRA)" <>
Subject [jira] Commented: (CXF-1145) Not able to set the namespace for a service wsdl
Date Tue, 30 Oct 2007 17:07:51 GMT


Tawfik Lachheb commented on CXF-1145:

Has anyone gotten a chance to take a look at this one?  If so, do we have an idea on the leve
of effort involved?

This is a show stopper for us.  We would prefer not to have to rollback to xfire in order
to get the production release going.  we have some minor issues with xfire that will probably
not get fixed.

> Not able to set the namespace for a service wsdl
> ------------------------------------------------
>                 Key: CXF-1145
>                 URL:
>             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
> 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