Reputation: 4165
Description Resource Path Location Type
WS-I: A problem occured while running the WS-I WSDL conformance check:
org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: null
Nested exception is:
java.lang.NullPointerException
The WSDLAnalyzer was unable to validate the given WSDL File.
ChangedElements.wsdl /wstest/WebContent/wsdl line 1 WSDL Problem
Update:
Netbeans gives this error:
cvc-elt.1: Cannot find the declaration of element 'wsdl:definitions'. [7]
The part of wsdl:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.example.org/xxx/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
name="xxx"
targetNamespace="http://www.example.org/xxx/">
Upvotes: 7
Views: 8973
Reputation: 598
Change the WSDL Definition to
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap"
xmlns:tns="http://www.example.org/xxx"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="xxx"
targetNamespace="http://www.example.org/xxx">
note the Trailing Slashes being removed
Upvotes: 2
Reputation: 6237
Look and vote at these bugs:
EDIT: I have found the problem - but the solution got stuck somewhere in WTP team:
Upvotes: 3
Reputation: 31
I'm having the same issue and it appears to be mainly on referencing dotnet WCF and WSE services.
The only thing I have found to work is to build up the WSDL manually.
Upvotes: 0