this isn't CXF. It looks like you're just using the 1.6 JDK builtin stuff.

On Thu, Nov 11, 2010 at 5:42 PM, Michael <[email protected]> wrote:
> Although I been working with web services for quite some time this is my 
> first attempt to create web services using CXF.  I'm starting with a very 
> simple service (Java first) and using a simple standalone Jave console app as 
> the client.
>
> My development environment is JDK 1.6, Java EE 6, Eclipse Helios (With WTP) 
> and Tomcat 6.
>
> When I run my client from Eclipse I get the following error:
>
> Exception in thread "main" javax.xml.ws.WebServiceException: Failed to access 
> the WSDL at:
>  http://localhost:8080/SimpleCXFWebServiceForTomcat/services/SimplePort?wsdl.
> It failed with:
>  http://localhost:8080/SimpleCXFWebServiceForTomcat/services/SimplePort?wsdl.
>  at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unknown 
> Source)
>  at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown 
> Source)
>  at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown Source)
>  at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown Source)
>  at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(Unknown Source)
>  at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknown 
> Source)
>  at javax.xml.ws.Service.<init>(Unknown Source)
>  at org.simple.ws.SimpleService.<init>(SimpleService.java:52)
>  at org.simple.ws.SimpleClient.main(SimpleClient.java:8)
> Caused by: java.io.FileNotFoundException:  
> http://localhost:8080/SimpleCXFWebServiceForTomcat/services/SimplePort?wsdl
>  at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
>  at java.net.URL.openStream(Unknown Source)
>  at 
> com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Unknown 
> Source)
>  at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unknown 
> Source)
>  ... 8 more
>
> Can someone please explain?
>
> Please let me know if you need source code sent to assist.
>
> Thanks,
> Mike
>

Reply via email to