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/404452"
< EclipseLink | Development
(New page: = Planning: MOXy JSON Schema Generation = [http://bugs.eclipse.org/404452 ER 404452] Currently EclipseLink supports generating XML Schemas from a JAXBContext. A feature will be added to ...) |
(→Phases) |
||
| Line 8: | Line 8: | ||
The development of this feature will need to be split into multiple phases. The current EclipseLink JSON support is insufficient to map to a json schema document. Additional enhancements will be required in order to generate these schemas. | The development of this feature will need to be split into multiple phases. The current EclipseLink JSON support is insufficient to map to a json schema document. Additional enhancements will be required in order to generate these schemas. | ||
| + | |||
| + | == Phase 1: Additional Mapping Support == | ||
| + | JSON Schemas in several places specify collections of data where the name of the element corresponds to a property in the object. This is something that is not currently supported by eclipselink's oxm/json binding layer. This would require adding support | ||
Revision as of 15:29, 5 April 2013
Planning: MOXy JSON Schema Generation
Currently EclipseLink supports generating XML Schemas from a JAXBContext. A feature will be added to generate JSON Schemas. At first this feature will be based on JAXB metadata and mappings, in the future this will be adapted to JSON-B metadata.
Phases
The development of this feature will need to be split into multiple phases. The current EclipseLink JSON support is insufficient to map to a json schema document. Additional enhancements will be required in order to generate these schemas.
Phase 1: Additional Mapping Support
JSON Schemas in several places specify collections of data where the name of the element corresponds to a property in the object. This is something that is not currently supported by eclipselink's oxm/json binding layer. This would require adding support