Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328155 - JAXB Externalized Metadata: Support for type on xml-elements
Summary: JAXB Externalized Metadata: Support for type on xml-elements
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-19 12:33 EDT by Rick Barkhouse CLA
Modified: 2022-06-09 10:29 EDT (History)
1 user (show)

See Also:

Attachments
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 2010-10-19 12:33:35 EDT 
In Dynamic JAXB we have no way of finding the type of the Java attribute
specified in an xml-elements element in OXM.  We will need to add a 'type' attribute to xml-elements, so that we can override the
java.lang.Object Java attribute that is initially present in Dynamic JAXB.
Comment 1 David McCann CLA 2010-10-21 14:29:32 EDT 
Since xml-elements is intended to be used on a collection, would you require container-type as well?
Comment 2 David McCann CLA 2010-10-25 15:15:11 EDT 
It appears as if we've already done container-type, so that is not an issue.  Type is however:  according to the spec, if the type is known then the XmlElements list has to be of size 1, and the rules for XmlElement mapping applies.  Type doesn't seem necessary in this case.
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:29:37 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink