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.
Difference between revisions of "EclipseLink/Development/MOXy"
< EclipseLink | Development
m (→EclipseLink2.3/3.0) |
(→EclipseLink2.5) |
||
| (29 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Roadmap == | == Roadmap == | ||
| + | === EclipseLink 2.6 === | ||
| + | The theme of this release is reducing MOXy's install footprint and supporting JSON schema. | ||
| + | |||
| + | [http://wiki.eclipse.org/EclipseLink/Development/2.6.0 2.6.0 Feature Summary] | ||
| + | |||
| + | ---- | ||
| + | |||
| + | === EclipseLink2.5 === | ||
| + | The theme of this release is RESTful services. Much of the work that was done was to make it easier for users to create RESTful services with MOXy easier either standalone or by leveraging JPA-RS. | ||
| + | |||
| + | [http://wiki.eclipse.org/EclipseLink/Development/2.5.0 2.5.0 Feature Summary] | ||
| + | |||
| + | * '''Performance''' | ||
| + | ** Numerous performance improvements were implemented in this release, ensuring MOXy continues to perform as a best-in-class XML & JSON binding solution. | ||
| + | * '''Bug backlog''' | ||
| + | ** [http://tinyurl.com/b65e83s EclipseLink2.5 MOXY, DBWS, SDO bugs: OPEN] | ||
| + | ** [http://tinyurl.com/babjb2b EclipseLink2.5 MOXY, DBWS, SDO bugs: RESOLVED] | ||
| + | ---- | ||
| + | |||
| + | === EclipseLink2.4 === | ||
| + | * '''Object binding to JSON''' | ||
| + | ** [http://wiki.eclipse.org/EclipseLink/DesignDocs/350483 Design doc] | ||
| + | * '''Glassfish/WLS Service Integrations''' | ||
| + | ** JAX-RS | ||
| + | *** Develop set of JAX-RS server tests for execution across supported app servers (starting with WLS, GF) | ||
| + | ** JAX-WS | ||
| + | *** JAX-WS CTS, TCK tests running using MOXy as JAXB binding provider in WLS environment | ||
| + | * Feature extensions | ||
| + | ** Set of feature mirroring JAXB RI extensions - each of these need to be validated and approved. | ||
| + | ** '''NamespacePrefixMapper''' (Matt) | ||
| + | *** The MOXy equivalent would be a interface that users could Implement to configure the NamespaceResolver. | ||
| + | ** '''@com.sun.xml.bind.annotation.OverrideAnnotationOf''' | ||
| + | ** '''@com.sun.xml.bind.annotation.XmlIsSet''' | ||
| + | *** This is comparable to existing @XmlIsSetNullPolicy | ||
| + | ** '''@com.sun.xml.bind.annotation.XmlLocation''' | ||
| + | *** This annotation is placed on a field /property of type Locator, and is used to capture the XML location of where the object is unmarshalled from. | ||
| + | ** '''com.sun.xml.bind.CycleRecoverable''' | ||
| + | *** Similar to MOXy’s @XmlInverseReference, except that it is an interface implemented by the POJO instead of an annotation. | ||
| + | ** '''com.sun.xml.bind.v2.model.annotation Locatable''' | ||
| + | *** Locatable forms a tree structure, where each Locatable points back to the upstream Locatable. For example, imagine Locatable X that points to a particular annotation, whose upstream is Locatable Y, which points to a particular method (on which the annotation is put), whose upstream is Locatable Z, which points to a particular class (in which the method is defined), whose upstream is Locatable W, which points to another class (which refers to the class Z), and so on. | ||
| + | ** '''com.sun.xml.bind.v2.runtime.reflect.AccessorFactory''' | ||
| + | *** Provides a way to provide a custom AttributeAccessor. | ||
| + | ** '''IDResolver''' | ||
| + | * Bug backlog | ||
| + | ** [http://tinyurl.com/65yvx4z EclipseLink2.4 MOXY, DBWS, SDO bugs: OPEN] | ||
| + | ** [http://tinyurl.com/68ndhge EclipseLink2.4 MOXY, DBWS, SDO bugs: RESOLVED] | ||
| + | ---- | ||
| + | |||
| + | === EclipseLink2.3 === | ||
| + | * JPA RESTful services | ||
| + | ** [http://wiki.eclipse.org/EclipseLink/DesignDocs/326663 JAX-RS integration design doc] | ||
| + | ** [http://wiki.eclipse.org/EclipseLink/Examples/REST REST examples] | ||
| + | * [http://wiki.eclipse.org/EclipseLink/Examples/MOXy/Extensible Extend entities] | ||
| + | ** Allow a user to start with a predesigned JAXBContext and add mappings to the entities without the need for the context to be recreated. | ||
| + | ** 339373 - Enhancement: Multiple Binding File Support. | ||
| + | ** 339383 - Enhancement: Persist metadata modifications made at runtime | ||
| + | ** 339377 - Enhancement: Programmatic means of adding mapping to an initialized XMLDescriptor at runtime | ||
| + | ** 339381 - Enhancement: XML Extensions. | ||
| + | * Mapping enhancements | ||
| + | ** [http://wiki.eclipse.org/EclipseLink/Examples/MOXy/MetadataRepository Externalize Mappings] | ||
| + | ** MOXy support for mapping with predicates | ||
| + | ** MOXy support for multiple eclipselink-oxm.xml mapping files | ||
| + | ** MOXy support for custom XML name conversions | ||
| + | * Integration points | ||
| + | ** JAX-WS2.0: TCK passing when using EclipseLink as JAXB provider | ||
| + | * Performance, Memory usage | ||
| + | ** Improvements to memory footprint associated with SDOHelperContext | ||
| + | ** Analysis of memory footprint when running in a Cloud service environment | ||
| + | * Customizable Name Mangling Algorithm | ||
| + | ** http://wiki.eclipse.org/EclipseLink/Development/333601 | ||
| + | * Bug backlog | ||
| + | ** [http://tinyurl.com/6ylwagb EclipseLink2.3 MOXY, DBWS, SDO bugs: OPEN] | ||
| + | ** [http://tinyurl.com/2g9c92y EclipseLink2.3 MOXY, DBWS, SDO bugs: RESOLVED] | ||
| + | ---- | ||
| + | |||
=== EclipseLink2.2 === | === EclipseLink2.2 === | ||
* Additional MOXy external metadata and annotation support | * Additional MOXy external metadata and annotation support | ||
| Line 19: | Line 94: | ||
* [http://tinyurl.com/23kkbln EclipseLink2.2 MOXY, SDO bugs: RESOLVED] | * [http://tinyurl.com/23kkbln EclipseLink2.2 MOXY, SDO bugs: RESOLVED] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
---- | ---- | ||
== Backlog of development items (MOXY, SDO)== | == Backlog of development items (MOXY, SDO)== | ||
| + | # Diagnostics, Logging | ||
| + | ## Similarly, need to improve this when being invoked within a Cloud service | ||
| + | # JAXB extensions | ||
| + | ## Identify features to continue to align ourselves with reference implementation | ||
| + | # Integration points | ||
| + | ## JAXB on Glassfish: Test our current level of support | ||
| + | ## Improve large document support | ||
| + | # OSGi testing strategy | ||
| + | ## Ability to create pure JAXB bundle | ||
# Performance | # Performance | ||
## Reduce use of Lexical Handler | ## Reduce use of Lexical Handler | ||
| − | |||
## SDO: Improve post processing of unmarshalling SDO Objects | ## SDO: Improve post processing of unmarshalling SDO Objects | ||
# SDO3.0 feature work | # SDO3.0 feature work | ||
| Line 69: | Line 122: | ||
# Bug backlog | # Bug backlog | ||
#* [http://tinyurl.com/2c2ytar MOXy,DBWS, SDO Future bugs] | #* [http://tinyurl.com/2c2ytar MOXy,DBWS, SDO Future bugs] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 09:25, 24 April 2013
Contents
Roadmap
EclipseLink 2.6
The theme of this release is reducing MOXy's install footprint and supporting JSON schema.
EclipseLink2.5
The theme of this release is RESTful services. Much of the work that was done was to make it easier for users to create RESTful services with MOXy easier either standalone or by leveraging JPA-RS.
- Performance
- Numerous performance improvements were implemented in this release, ensuring MOXy continues to perform as a best-in-class XML & JSON binding solution.
- Bug backlog
EclipseLink2.4
- Object binding to JSON
- Glassfish/WLS Service Integrations
- JAX-RS
- Develop set of JAX-RS server tests for execution across supported app servers (starting with WLS, GF)
- JAX-WS
- JAX-WS CTS, TCK tests running using MOXy as JAXB binding provider in WLS environment
- JAX-RS
- Feature extensions
- Set of feature mirroring JAXB RI extensions - each of these need to be validated and approved.
- NamespacePrefixMapper (Matt)
- The MOXy equivalent would be a interface that users could Implement to configure the NamespaceResolver.
- @com.sun.xml.bind.annotation.OverrideAnnotationOf
- @com.sun.xml.bind.annotation.XmlIsSet
- This is comparable to existing @XmlIsSetNullPolicy
- @com.sun.xml.bind.annotation.XmlLocation
- This annotation is placed on a field /property of type Locator, and is used to capture the XML location of where the object is unmarshalled from.
- com.sun.xml.bind.CycleRecoverable
- Similar to MOXy’s @XmlInverseReference, except that it is an interface implemented by the POJO instead of an annotation.
- com.sun.xml.bind.v2.model.annotation Locatable
- Locatable forms a tree structure, where each Locatable points back to the upstream Locatable. For example, imagine Locatable X that points to a particular annotation, whose upstream is Locatable Y, which points to a particular method (on which the annotation is put), whose upstream is Locatable Z, which points to a particular class (in which the method is defined), whose upstream is Locatable W, which points to another class (which refers to the class Z), and so on.
- com.sun.xml.bind.v2.runtime.reflect.AccessorFactory
- Provides a way to provide a custom AttributeAccessor.
- IDResolver
- Bug backlog
EclipseLink2.3
- JPA RESTful services
- Extend entities
- Allow a user to start with a predesigned JAXBContext and add mappings to the entities without the need for the context to be recreated.
- 339373 - Enhancement: Multiple Binding File Support.
- 339383 - Enhancement: Persist metadata modifications made at runtime
- 339377 - Enhancement: Programmatic means of adding mapping to an initialized XMLDescriptor at runtime
- 339381 - Enhancement: XML Extensions.
- Mapping enhancements
- Externalize Mappings
- MOXy support for mapping with predicates
- MOXy support for multiple eclipselink-oxm.xml mapping files
- MOXy support for custom XML name conversions
- Integration points
- JAX-WS2.0: TCK passing when using EclipseLink as JAXB provider
- Performance, Memory usage
- Improvements to memory footprint associated with SDOHelperContext
- Analysis of memory footprint when running in a Cloud service environment
- Customizable Name Mangling Algorithm
- Bug backlog
EclipseLink2.2
- Additional MOXy external metadata and annotation support
- Overview
- Design Doc Links
- Phase 1 - Provide MOXy annotation support equivalent to our XML metadata support
- Phase 2.1 - Additional MOXy annotation/xml metadata support
- Phase 3 - MOXy Equivalents of Relevant JPA Annotations
- MOXy Dynamic Persistence
- User documentation
- Continual improvements based on User Guide ToC outline
- Integration points/mash-ups
- JAXB: JAX-RS integration
- Spring support for MOXy component
- Marshalling to/from JSON, YAML
- EclipseLink2.2 MOXY, SDO bugs: OPEN
- EclipseLink2.2 MOXY, SDO bugs: RESOLVED
Backlog of development items (MOXY, SDO)
- Diagnostics, Logging
- Similarly, need to improve this when being invoked within a Cloud service
- JAXB extensions
- Identify features to continue to align ourselves with reference implementation
- Integration points
- JAXB on Glassfish: Test our current level of support
- Improve large document support
- OSGi testing strategy
- Ability to create pure JAXB bundle
- Performance
- Reduce use of Lexical Handler
- SDO: Improve post processing of unmarshalling SDO Objects
- 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
- Bug backlog