Hi Dan, Same error no matter how I use the jetty plugin (run, run-war, run-exploded). The only one I haven't tried is run-inplace, but that one scares me. ;)
No worries-- I'll just throw the wsdl in the classpath-- not a super big deal. Thanks for the suggestions though. -Chris -----Original Message----- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 25, 2007 10:50 AM To: cxf-user@incubator.apache.org Subject: Re: Maven2 Jetty Plugin Problem Finding WSDL Hmm.... this "sounds" like an issue with the Jetty plugin not providing the proper JNDI based URL for the wsdl. Can you try running "mvn jetty:run-war" and "mvn jetty:run-exploded" and see if it's different? I've honestly never used the embedded jetty stuff so I don't really know what it's doing. Dan On Tuesday 24 April 2007 17:23, Christopher Moesel wrote: > It's a shot in the dark but... > > My wsdl-first CXF service specifies the WSDL location like so: > wsdlLocation="WEB-INF/myservice.wsdl" > > In my project (which uses Maven2), the wsdl file is indeed at: > C:/projects/mywebservice/src/main/webapp/WEB-INF/myservice.wsdl > > If I do a mvn:install and hand-deploy the .war to jboss or tomcat, it > works great. > > If I try using the embedded Jetty plugin, it fails: > mvn jetty:run > causes: > Caused by: java.io.FileNotFoundException: > C:/projects/mywebservice/WEB-INF/myservice.wsdl (The system cannot > find the path specified) > > Note that it searches for the wsdl relative to the project root rather > than the webapp root. Does anyone know how to fix it? Thus far, the > only way I can get it is to have it load the WSDL from the classpath > instead. > > -Chris -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
