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

EclipseLink/Development/MOXy

Roadmap

EclipseLink2.2


EclipseLink2.3/3.0

  • JPA RESTful services
  • Performance, Memory usage
    • Analysis of competitive performance
    • Analysis of memory footprint when running in a Cloud service environment
  • JAXB extensions
    • Identify features to continue to align ourselves with reference implementation
  • Integration points/mash-ups
    • JAX-WS2.0: Integration with EclipseLink JAXB
    • JAXB on Glassfish: Test our current level of support
    • Improve large document support
    • Improve logging, exception handling
  • OSGi testing strategy
    • Ability to create pure JAXB bundle
  • Bug backlog

Backlog of development items (MOXY, SDO)

  1. Performance
    1. Reduce use of Lexical Handler
    2. SDO: Improve ChangeSummary processing
    3. SDO: Improve post processing of unmarshalling SDO Objects
  2. 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
  3. Bug backlog
    • MOXy,DBWS, 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