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

Bug 353596

Summary: Issue when using @XmlIDREF with @XmlAdapter
Product: z_Archived Reporter: Blaise Doughan <blaise.doughan>
Component: EclipselinkAssignee: Nobody - feel free to take it <nobody>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P4 CC: it-utvikling
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
URL: http://stackoverflow.com/questions/6882337/xmladapter-and-xmlidref-in-moxy-jaxb
Whiteboard:
Attachments:
Description Flags
Code demonstrating the bug none

Description Blaise Doughan CLA 2011-08-02 10:33:36 EDT 
There is an issue when using @XmlIDREF with XmlAdapter.  The issue is that if the adapted object makes use of @XmlIDREF, the @XmlIDREF will not have been processed at the time the XmlAdapter logic is run.
Comment 1 Blaise Doughan CLA 2011-08-02 10:35:33 EDT 
Created attachment 200721 [details]
Code demonstrating the bug
Comment 2 Blaise Doughan CLA 2012-05-01 10:09:52 EDT 
Re-targeting to "Future" for consideration in another release.

Core Issue:
The core issue is determining the order in which XmlAdapters should be applied.  If the value object has an @XmlIDREF annotation then we may need to delay the conversion until after the references have been resolved.

Additional Use Cases:
In addition to the issue demonstrated in the attached code we need to decide what to do when an adapted object contains both an @XmlID and @XmlIDREF.
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:28:55 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink