Community
Participate
Working Groups
When MAX retrieves WSDL that it doesn't like, it fails with generic error messages such as unable to connect to resource. This gives no information whatsoever regarding the cause of the error. Some additional information should be provided. It should state that there was a problem parsing WSDL. It should attempt to state the section of the WSDL which caused the failure, ie schema, operation x, message y, etc. Anything is better than what is currently produced.
Target to iteration 2 as per Balan's spreadsheet.
This will be resolved by putting our error messages that the received metadata is invalid and also point to the WSDL. However advanced WSDL error reporting may not be available. MAX in this release will not serve as a complete endpoint validation tool at this level of granularity.
If unable to connect MAX, error message shows in the error log build: tptpaide-2007-03-09-05-00-00
Created attachment 65143 [details] Does MEX first before SG or relationships, reuses WSDLs retrieved over MEX
Created attachment 65228 [details] Patch to open error log Please apply the patch.
All errors that the Muse runtime returns are shown in the error log. Opening https://bugs.eclipse.org/bugs/show_bug.cgi?id=185625 to track opening of error log automatically. Also moving the patch for the safe (4/27 from Saurabh) to the other bug. Closing this one out as the primary problem is resolved.
Verified - fixed TPTP-4.4.0-200705080100
Changing OS from Mac OS to Mac OS X as per bug 185991