| Summary: | JAXB Externalized Metadata: Support for type on xml-transformation | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Rick Barkhouse <rick.barkhouse> |
| Component: | Eclipselink | Assignee: | Project Inbox <eclipselink.oxm-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | david.mccann, rick.barkhouse |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Rick Barkhouse
Is container-type required as well? Hi Dave, you're right, we would need container-type as well, as the xml-transformation is responsible for completely defining the Java attribute. Is this support still required? 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. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |