Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331159 - Object not set on ValidationEventLocator
Summary: Object not set on ValidationEventLocator
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: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-25 16:53 EST by Blaise Doughan CLA
Modified: 2022-06-09 10:32 EDT (History)
0 users

See Also:

Attachments
Core - Fix (16.27 KB, patch)
2010-12-08 11:56 EST, Blaise Doughan CLA 		no flags Details | Diff
MOXy - Fix (10.57 KB, patch)
2010-12-08 11:56 EST, Blaise Doughan CLA 		no flags Details | Diff
MOXy - Test Cases (23.63 KB, patch)
2010-12-08 16:21 EST, Blaise Doughan 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 Blaise Doughan CLA 2010-11-25 16:53:13 EST 
When a ValidationEvent is thrown on a marshal operation, the correponding object is not being set on the ValidationEventLocator.
Comment 1 Blaise Doughan CLA 2010-12-08 11:56:29 EST 
Created attachment 184797 [details]
Core - Fix
Comment 2 Blaise Doughan CLA 2010-12-08 11:56:49 EST 
Created attachment 184798 [details]
MOXy - Fix
Comment 3 Blaise Doughan CLA 2010-12-08 16:21:24 EST 
Created attachment 184818 [details]
MOXy - Test Cases
Comment 4 Blaise Doughan CLA 2010-12-09 10:38:43 EST 
Code checked into trunk at rev:  8670

Code reviewed by:  Matt MacIvor

Fix details:

ValidatingMarshalRecord
- Introduced a subclass of SAXParseException (ValidatingMarshalRecord.MarshalSAXParseException) with a property for holding the relevant object.
- Introduced an ErrorHandler that converts instances of SAXParseException to MarshalSAXParseException.  The relevant object is obtained from the MarshalRecord.

MarshalRecord
- The MarshalRecord was not maintaining the correct owning object.  This has been addressed by adding two new methods to marshal record:  beforeContainmentMarshal & afterContainmentMarshal.
- These methods are also responsible for call the Marshal Listener.

Node Values
- These classes have been updated to call the new methods on MarshalRecord.
Comment 5 Eclipse Webmaster CLA 2022-06-09 10:16:34 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
Comment 6 Eclipse Webmaster CLA 2022-06-09 10:32:17 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink