Community
Participate
Working Groups
Build Identifier: I20101208-1300 There are two different port types, two bindings and two ports in one wsdl:service. All of them use WS-Addressing Metadata. When I comment one port in wsdl:service the NPE is gone. I've traced the problem down to: - assertion BP2402 is tested - list of prerequisites is checked (which is [ BP2703 ]) - org.eclipse.wst.wsi.internal.core.report.impl.ReportImpl.getAssertionResult(String) returns null, because "currentEntry.getEntryContainer().getAssertionResult(assertionId)" returns null WS-I Compliance Checker from SOAPUI works fine for the attached WSDLs/XSDs Reproducible: Always Steps to Reproduce: 1. Open attached WSDLs/XSDs 2. Validate 3. See NPE
Created attachment 186599 [details] Here are the WSDLs causing NPE during WS-I validation
Reducing severity since this isn't a major loss of function.
It's the same bug as https://bugs.eclipse.org/bugs/show_bug.cgi?id=323157
Created attachment 219804 [details] a perfectly valid WSDL from Apache ODE samples This bug is truly unacceptable. It makes the WSDL Editor useless on many perfectly valid files used all over the industry. Attached example is from Apache ODE. This is also a painfully-old bug--what is it going to take to get it fixed? Validation Problem Error: "A problem occurred while running the WSDL validator for namespace http://schemas.xmlsoap.org/wsdl/."
It's the same bug asAre we sure that this is the same as https://bugs.eclipse.org/bugs/show_bug.cgi?id=323157? How can we help with this one?
