Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/Development/MOXy
< EclipseLink | Development
Revision as of 15:57, 23 June 2010 by Unnamed Poltroon (Talk) (→Backlog of development items (MOXY, SDO))
Roadmap
EclipseLink2.2
EclipseLink3.0
Backlog of development items (MOXY, SDO)
- MOXy External Metadata
- Annotation support for MOXy advanced mappings
- Support entries from deployment.xml that are currently not represented in external XML file
- Transformation, Inverse mappings
- MOXy Dynamic Persistence
- Bootstrapping from external OXM file
- SDO3.0 feature work
- New bootstrap API
- Improve class generation to include new SDO 3.0 annotations
- Enhanced key based relationships
- Composite keys
- Embedded key objects
- Property Improvements
- XML XPath based property access
- Orphan properties
- Enum support
- Import - Moving DataObjects between HelperContexts
- OSGi testing strategy
- Ability to create pure JAXB bundle
- MOXy: Provide native support for Orphan list
- Performance
- Reduce use of Lexical Handler
- SDO: Improve ChangeSummary processing
- SDO: Improve post processing of unmarshalling SDO Objects
- Integration points/mash-ups
- JAX-WS2.0: Integration with EclipseLink JAXB
- JAXB: JAX-RS integration
- Investigate Spring support for MOXy component
- Marshalling to/from JSON, YAML
- Improve large document support
- Improve logging, exception handling
- Bug backlog
- MOXy, SDO Future bugs
- Enhancement/External requests
- 235850 Allow user to specify that text values should be trimmed
- 280779 Converting SDO object to SDO/JAXB object
- 298220 Overriding mapped xpaths for composite objects
- 269045 Need better error message for NoSuchElementException
- 298125 Add ability to map collection of elements with different names
- 301232 Need an API to persist SDO Change Summary to XML