Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 167280

Summary:

Insufficient error reporting when parsing WSDL

Product:

z_Archived

Reporter:

davidmelgar

Component:

TPTP.monitoring

Assignee:

Balan Subramanian <bsubram>

Status:

CLOSED FIXED

QA Contact:

Bhanu Prathap V <bhanu.prathap>

Severity:

major

Priority:

CC:

bsubram

Version:

unspecified

Keywords:

plan

Target Milestone:

---

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

Attachments:

Description	Flags
Does MEX first before SG or relationships, reuses WSDLs retrieved over MEX	none
Patch to open error log	none

Description davidmelgar

2006-12-08 14:33:51 EST

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.

Comment 1 Dave Smith

2007-02-06 16:13:31 EST

Target to iteration 2 as per Balan's spreadsheet.

Comment 2 Balan Subramanian

2007-02-07 20:37:15 EST

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.

Comment 3 Bhanu Prathap V

2007-03-14 02:33:38 EDT

If unable to connect MAX, error message shows in the error log
build: tptpaide-2007-03-09-05-00-00

Comment 4 Balan Subramanian

2007-04-26 23:50:04 EDT

Created attachment 65143 [details]
Does MEX first before SG or relationships, reuses WSDLs retrieved over MEX

Comment 5 Saurabh Dravid

2007-04-27 12:35:15 EDT

Created attachment 65228 [details]
Patch to open error log

Please apply the patch.

Comment 6 Balan Subramanian

2007-05-04 18:36:27 EDT

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.

Comment 7 Bhanu Prathap V

2007-05-09 12:22:11 EDT

Verified - fixed
TPTP-4.4.0-200705080100

Comment 8 Eclipse Webmaster

2007-07-29 09:21:17 EDT

Changing OS from Mac OS to Mac OS X as per bug 185991