Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326710 - JAXB Externalized Metadata: Support for type on xml-transformation
Summary: JAXB Externalized Metadata: Support for type on xml-transformation
Status: RESOLVED INVALID
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: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-30 15:48 EDT by Rick Barkhouse CLA
Modified: 2022-06-09 10:07 EDT (History)
2 users (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-09-30 15:48:14 EDT 
In Dynamic JAXB we have no way of finding the type of the Java attribute specified in an xml-transformation element in OXM.  We will need to add a 'type' attribute to xml-transformation, 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-01 09:49:21 EDT 
Is container-type required as well?
Comment 2 Rick Barkhouse CLA 2010-10-01 10:03:32 EDT 
Hi Dave, you're right, we would need container-type as well, as the xml-transformation is responsible for completely defining the Java attribute.
Comment 3 David McCann CLA 2010-10-25 09:21:17 EDT 
Is this support still required?
Comment 4 Rick Barkhouse CLA 2010-10-25 15:41:15 EDT 
After further thought, we will not be supporting the XmlTransformation case in Dynamic JAXB, as it is not compatible with a class-less, dynamic model.
Comment 5 Eclipse Webmaster CLA 2022-06-09 10:07:30 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink