Likely not via easy spring configuration. You can add name="Manager" to the @WebService annotation on the ManagerWS interface and that should definitely do it, but that obviously involves a little bit of code changes.
Dan On Aug 27, 2012, at 8:11 PM, purecharger <[email protected]> wrote: > I recently upgraded to CXF 2.6.2 from 2.2, and in doing so I separated a > single web service interface into two interfaces and also changing the name > of the top level interface used in the deployment descriptor. > > before: > > interface name = Manager > > after: > > interface name = ManagerWS > and interface Manager extends ManagerWS > > Here is my jax-ws descriptor: > > <jaxws:endpoint id="Manager" > xmlns:s="http://api.mycompany.com/"; > serviceName="s:Manager" name="Manager" > implementorClass="com.mycompany.ManagerWS" > endpointName="s:Manager" > implementor="#Manager" > address="/Manager" /> > > The problem I have now is that the new class name causes the <wsdl:location > /> to be different, and existing clients break due to the changed port name: > > <wsdl:import > location="http://localhost:8080/DEV/ws/services/soap/Manager?wsdl=ManagerWS.wsdl"; > namespace="http://api.mycompany.com/";> > > Is it possible to control the WSDL name of this service so that I can keep > it as 'Manager', allowing existing clients to work as before? > > Ryan > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Controlloing-WSDL-location-name-tp5713181.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
