Turns out I was just not *seeing* the WSDL because apparently Chrome doesn't display WSDL. When viewed in Firefox / page source, it displayed fine!
Zwei Steinen wrote: > > Hi, I am trying to implement a simple web service provider using Tomcat6, > CXF 2.2, Spring 3, and actually the service itself runs fine (I can call > web methods using the original WSDL and SoapUI). However, Tomcat returns a > blank page on "?wsdl" requests. I used "contract first" style. Does CXF > not generate WSDL if contract-first is used? If so, what is the best > practice to publish WSDL in such case? > > EDIT: What I did so far: > > 1.Setup tomcat6 with Spring3 > 2.Generate CXF implementation class by using maven > 3.Provide web.xml (only relevant part shown) > > <listener> > > <listener-class>org.springframework.web.context.ContextLoaderListener > </listener-class> > </listener> > > <servlet> > <servlet-name>cxf</servlet-name> > <servlet-class> > org.apache.cxf.transport.servlet.CXFServlet > </servlet-class> > <load-on-startup>1</load-on-startup> > </servlet> > > <servlet-mapping> > <servlet-name>cxf</servlet-name> > <url-pattern>/*</url-pattern> > </servlet-mapping> > </web-app> > 4.Provide applicationContext.xml (only relevant part is shown) > > <import resource="classpath:META-INF/cxf/cxf.xml"/> > <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml"/> > <import resource="classpath:META-INF/cxf/cxf-servlet.xml"/> > > <jaxws:endpoint > id="service" > implementor="org.sample.ServiceImpl" > implementorClass="org.sample.ServiceImpl" > address="/service"/> > 5.Package generated stuff into war and deploy > > > Thank you very much in advance. > > *This question was also asked in stackoverflow.com > -- View this message in context: http://old.nabble.com/How-to-publish-%28flat%29-WSDL-in-contract-first-approach-%28using-CXF-2.2%2C-Spring-3%2C-Tomcat6%29-tp28261876p28261975.html Sent from the cxf-user mailing list archive at Nabble.com.
