[XSTR-37] Provide context information on errors

Details

Type: Improvement
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 0.1
Fix Version/s: 1.0
Component/s: Core
Labels:
None

Description

When an error occurs during the serialization/deserialization phase, the error should contain context of where in the hierarchical stream the error occurred to aid debugging by the user.

For instance, an XPath expression:
/person/address[4]/areacode : Couldn't convert 'blah' to int.

Activity

Hide

Permalink

Joe Walnes added a comment - 08/May/04 6:22 AM

I would like to see as much as possible in the error that could aid in debugging. Things such as:

Line number in XML (if available)
XPath of currenty error: /something/another[3]/blah
Converter that caused problem: FooConverter
Stack trace
Class of object that is being manipulated: com.blah.MyFoo
Field (if applicable) or item number that failed: Field name, or element 7

Show

Joe Walnes added a comment - 08/May/04 6:22 AM I would like to see as much as possible in the error that could aid in debugging. Things such as: Line number in XML (if available) XPath of currenty error: /something/another [3] /blah Converter that caused problem: FooConverter Stack trace Class of object that is being manipulated: com.blah.MyFoo Field (if applicable) or item number that failed: Field name, or element 7

People

Assignee:

Joe Walnes

Reporter:

Joe Walnes

Votes:

0 Vote for this issue

Watchers:

0 Start watching this issue

Dates

Created:

19/Mar/04 8:47 AM

Updated:

08/May/04 1:41 PM

Resolved:

08/May/04 1:41 PM