Can you share your cxf endpoint configuration with us? Best, Christian
On Fri, Dec 14, 2012 at 12:53 PM, Sachin <sachin2...@gmail.com> wrote: > Hi I am using Camel 2.9.1 with CXF 2.4.2. > I am facing this issue where CXF is generating it's own wsdl and exposing > it > inspite of what i provided. Only differnce between these two wsdls is that > CXF generated one doesnt have any wsdl: types defined in it.Which causing > problem while accesing this web service using ..?wsdl url. > > So how can we specify in camel-cxf to stop CXF to generate it's own wsdl. > In > plain CXF we can do that by > attribute wsdlLocation in the element jaxws:endpoint > > > CXF WSDL: > > wsdl:definitions name="CDSCompactService" > targetNamespace="http://mustservice.summit";> > <wsdl:types> </wsdl:types> > <wsdl:message name="NewTradeResponse">........ > > Actual WSDL: > <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:tns="http://mustservice.summit"; > xmlns:xsd1="http://mustservice.summit/NewTrade"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="CDSCompactService" > targetNamespace="http://mustservice.summit";> > <wsdl:types> > <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > <xsd:import namespace="http://mustservice.summit/NewTrade"; > schemaLocation="mustservice/summit/NewTrade/NewTrade.xsd"> > </xsd:import></xsd:schema> > </wsdl:types> > <wsdl:message name="NewTradeRequest">..... > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-to-stop-CXF-to-generate-it-s-own-wsdl-tp5724084.html > Sent from the Camel - Users mailing list archive at Nabble.com. > --
