Difference between revisions of "EclipseLink/Development/MOXy"

Revision as of 12:54, 13 April 2011

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
- Bootstrapping from external OXM file
- Documentation and Examples
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

JPA RESTful services
- JAX-RS integration design doc
- REST examples
Extensibility
- 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.
Performance, Memory usage
- Analysis of competitive performance
- Analysis of memory footprint when running in a Cloud service environment
Customizable Name Mangling Algorithm
- http://wiki.eclipse.org/EclipseLink/Development/333601
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
- JAX-WS2.0: Integration with EclipseLink JAXB
- JAXB on Glassfish: Test our current level of support
- Improve large document support
OSGi testing strategy
- Ability to create pure JAXB bundle
Bug backlog
- EclipseLink2.3 MOXY, DBWS, SDO bugs: OPEN
- EclipseLink2.2 MOXY, DBWS, SDO bugs: RESOLVED

Performance
1. Reduce use of Lexical Handler
2. SDO: Improve ChangeSummary processing
3. 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
- 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

@@ Line 25: / Line 25: @@
 ** [http://wiki.eclipse.org/EclipseLink/DesignDocs/326663 JAX-RS integration design doc]
 ** [http://wiki.eclipse.org/EclipseLink/Examples/REST REST examples]
+* Extensibility
+** 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.
 * Performance, Memory usage
 ** Analysis of competitive performance
 ** Analysis of memory footprint when running in a Cloud service environment
+* Customizable Name Mangling Algorithm
+** http://wiki.eclipse.org/EclipseLink/Development/333601
 * Diagnostics, Logging
 ** Similarly, need to improve this when being invoked within a Cloud service