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.
Difference between revisions of "EclipseLink/Development/MOXy"
< EclipseLink | Development
m |
m (→EclipseLink2.5) |
||
Line 7: | Line 7: | ||
** [http://wiki.eclipse.org/EclipseLink/Development/396542 Design doc] | ** [http://wiki.eclipse.org/EclipseLink/Development/396542 Design doc] | ||
*** Allow a subset of attributes to be marshaled and unmarshaled | *** Allow a subset of attributes to be marshaled and unmarshaled | ||
− | * Performance | + | * Performance |
** Numerous performance improvements were implemented in this release, ensuring MOXy continues to perform as a best-in-class XML & JSON binding solution. | ** Numerous performance improvements were implemented in this release, ensuring MOXy continues to perform as a best-in-class XML & JSON binding solution. | ||
* Bug backlog | * Bug backlog |
Revision as of 11:33, 6 February 2013
Contents
Roadmap
EclipseLink2.5
- MOXy bundle restructuring
- Design doc
- Separate MOXy bundles from other EclipseLink components to reduce install size and simplify bundling with other 3rd party products.
- Design doc
- MOXy NamedObjectGraphs
- Design doc
- Allow a subset of attributes to be marshaled and unmarshaled
- Design doc
- 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