Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362802 - XmlLocation inconsistencies depending on XML Parser used
Summary: XmlLocation inconsistencies depending on XML Parser used
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Rick Barkhouse CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-03 10:55 EDT by Rick Barkhouse CLA
Modified: 2022-06-09 10:13 EDT (History)
0 users

See Also:

Attachments
Patch (4.95 KB, patch)
2011-11-03 12:50 EDT, Rick Barkhouse CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Barkhouse CLA 2011-11-03 10:55:18 EDT 
It appears that different parsers return take different approaches when returning the XML Location of a given element.  The standard XML parser considers the end of the opening tag as the beginning of the element (eg L15 C89), whereas Woodstox and XDK use the beginning of the opening tag (eg. L15 C29).

The test cases should take this into account and accept both locations.
Comment 1 Rick Barkhouse CLA 2011-11-03 12:50:17 EDT 
Created attachment 206420 [details]
Patch
Comment 2 Rick Barkhouse CLA 2011-11-03 12:52:36 EDT 
Fixed, reviewed by bdoughan.
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:13:54 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink