Community
Participate
Working Groups
When validating a WSDL document with WS-I validation set to suggest or require the WS-I test tools produce the following error message that is not very useful to end users if the TADs cannot be obtained: WS-I: A problem occurred while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException. The WS-I Test Assertion Document(TAD) was not found or could not be processed. The WSDLAnalyzer was not able to validate the given WSDL file. Users have trouble understanding what this error means and what to do to correct it. (See [1].) This error message should be made more user friendly instructing them what to do or pointing them to some documentation. [1]http://dev.eclipse.org/newslists/news.eclipse.webtools/msg14956.html Steps to reproduce: 1. Disconnect from the Internet. 2. Launch a new workspace with WTP. 3. Create a new Dynamic Web project and create a new WSDL file in the project. (The name and contents of the WSDL file are unimportant. The WSDL file must contain valid WSDL though, as generated by the wizard.) 4. Ensure that WS-I validation is set to suggest or require. Validate the WSDL file. The error message is produced.
(In reply to comment #0) > When validating a WSDL document with WS-I validation set to suggest or require > the WS-I test tools produce the following error message that is not very useful > to end users if the TADs cannot be obtained: > > WS-I: A problem occurred while running the WS-I WSDL conformance check: > org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException. The WS-I Test > Assertion Document(TAD) was not found or could not be processed. The > WSDLAnalyzer was not able to validate the given WSDL file. > > Users have trouble understanding what this error means and what to do to > correct it. (See [1].) This error message should be made more user friendly > instructing them what to do or pointing them to some documentation. > > [1]http://dev.eclipse.org/newslists/news.eclipse.webtools/msg14956.html Ideally, it would just prompt them to download the TADs if it can't get them. Is there a reason, why the initial TADs aren't distributed with the plugin? Are there IP issues?
I agree. I think a pointer to a doc that describes how to download the TADs and add them to the XML catalog would be useful. WRT IP issues, there were issues when we tried to bundle the TADs back in (I think) 1.0. Given that we worked around the IP issues with the Java EE schemas and DTDs perhaps it's time to try again to bundle the TADs.
Hello. I am not proposing a solution to this problem here. Like others I believe the error message should be meaningful. However, unless I am mistaken the following may provide some additional useful information. I am doing this from MyEclipse. Slide your mouse across the icons on the top toolbar until you find and open 'Launch Web Services Explorer.' When that view opens slide your mouse across the icons in the top right of that window until you find and open 'WSDL Page.' Question? Why are these ghosted out until you move your mouse over them? Ghosted out implies they are not active to me. When the left-hand side changes to 'WSDL Main' click on that link and the right-hand side will change to a window that has a box for you to enter the URL of your WSDL (ie. http://localhost:7001/MyService/MyService?WSDL. Enter your WSDL URL, click the GO button and with any luck more error information will be displayed in the 'Status' portion of the view.
*** Bug 254438 has been marked as a duplicate of this bug. ***
Bug 254438 asks for the message to be displayed in the problems view and the graphical view.
