Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Development/MOXy"

m (EclipseLink2.2)
m (Backlog of development items (MOXY, SDO))
Line 57: Line 57:
 
# JAXB extensions
 
# JAXB extensions
 
## Identify features to continue to align ourselves with reference implementation
 
## Identify features to continue to align ourselves with reference implementation
 +
# Large document support
 +
## Determine our current level of support for handling large documents and identify areas for improvement
 
# Integration points/mash-ups
 
# Integration points/mash-ups
 
## JAX-WS2.0: Integration with EclipseLink JAXB
 
## JAX-WS2.0: Integration with EclipseLink JAXB

Revision as of 16:37, 23 June 2010

Roadmap

EclipseLink2.2

  • MOXy External Metadata
    • Annotation support for MOXy advanced mappings . Estimate required
  • MOXy Dynamic Persistence
    • Bootstrapping from external OXM file. Estimate required.
  • OSGi testing strategy
    • Ability to create pure JAXB bundle
  • SDO3.0 feature work
    • Content TBD
  • JAXB extensions
    • Content TBD
  • Performance
    • Needs scoping out to determine targets for this release
  • User documentation
  • 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
      • Needs scoping out to determine targets for this release
  • EclipseLink2.2 MOXY, SDO bugs: OPEN
    • "Future bugs" need to be reviewed.
  • EclipseLink2.2 MOXY, SDO bugs: RESOLVED

EclipseLink3.0


Backlog of development items (MOXY, SDO)

  1. 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
  2. MOXy Dynamic Persistence
    • Bootstrapping from external OXM file
  3. 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
  4. OSGi testing strategy
    • Ability to create pure JAXB bundle
  5. Performance
    1. Reduce use of Lexical Handler
    2. SDO: Improve ChangeSummary processing
    3. SDO: Improve post processing of unmarshalling SDO Objects
  6. JAXB extensions
    1. Identify features to continue to align ourselves with reference implementation
  7. Large document support
    1. Determine our current level of support for handling large documents and identify areas for improvement
  8. Integration points/mash-ups
    1. JAX-WS2.0: Integration with EclipseLink JAXB
    2. JAXB: JAX-RS integration
    3. Investigate Spring support for MOXy component
    4. Marshalling to/from JSON, YAML
    5. Improve large document support
    6. Improve logging, exception handling
  9. 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

Back to the top