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/339373"
| Line 23: | Line 23: | ||
= Configuration = | = Configuration = | ||
| + | |||
| + | Currently MOXy allows external bindings files to be passed in through a map of properties. MOXy allows one bindings file per package. The files can be passed into through the properties in 3 formats | ||
| + | |||
| + | # A Map of Input Sources keyed on package name. | ||
| + | # A list of Input Sources, one per package. | ||
| + | # A single Input Source. | ||
| + | |||
| + | To support multiple bindings files for a single package, this will be changed to allow the following additional options: | ||
| + | |||
| + | # A Map of Lists of Input Sources, keyed on package name. (Map<String, List<Object>>) | ||
| + | # Allow the list of Input Sources from #2 above to contain more than entry per package. | ||
Revision as of 14:32, 1 April 2011
Design Specification: Multiple Bindings File Support
Currently MOXy provides the ability to augment the annotation metadata with an XML bindings file. This enhancement request is for the ability to apply multiple binding files to a model.
Sample use case: 1. Initial metadata is specified with annotations. 2. Second version modifies the metadata with an XML bindings file. 3. Subsequent versions continue to modify the metadata with new bindings files.
With the metadata layered in this way a JAXBContext could be created to represent any version of the XML document.
Requirements
- Must provide an API to allow multiple bindings files to be passed into the context creation
- Be able to merge multiple bindings files into a single unified XmlBindings
- Must coincide with JPA rules for overrides with multiple orm .xml files.
Configuration
Currently MOXy allows external bindings files to be passed in through a map of properties. MOXy allows one bindings file per package. The files can be passed into through the properties in 3 formats
- A Map of Input Sources keyed on package name.
- A list of Input Sources, one per package.
- A single Input Source.
To support multiple bindings files for a single package, this will be changed to allow the following additional options:
- A Map of Lists of Input Sources, keyed on package name. (Map<String, List<Object>>)
- Allow the list of Input Sources from #2 above to contain more than entry per package.