Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/MOXy/MeetInTheMiddle"

(Overview)
m (Overview)
Line 8: Line 8:
 
* '''[[EclipseLink/Examples/MOXy/XMLNameTransformer|XMLNameTransformer]]''' - Customized XML Name Conversions.
 
* '''[[EclipseLink/Examples/MOXy/XMLNameTransformer|XMLNameTransformer]]''' - Customized XML Name Conversions.
 
* '''[[EclipseLink/Examples/MOXy/ElementMappingByAttributeValue|ElementMappingByAttributeValue]]''' - Mapping elements based on the value of an attribute.
 
* '''[[EclipseLink/Examples/MOXy/ElementMappingByAttributeValue|ElementMappingByAttributeValue]]''' - Mapping elements based on the value of an attribute.
* '''[[EclipseLink/Examples/MOXy/MetadataRepository|MetadataRepository]]''' - XML mapping document is an alternative to using annotations.
+
* '''[[EclipseLink/Examples/MOXy/MetadataRepository|MetadataRepository]]''' - Retrieve and use XML binding definitions from outside your application.

Revision as of 14:28, 15 June 2011

Overview

This set of examples is intended to introduce you to meet-in-the-middle mapping. This is when you are mapping an existing object model to an existing XML schema. This can commonly occur when you have an existing application that you wish to expose as a web service using a XML schema corresponding to some industry standard.

  • Advantages - Compare meet-in-the-middle mapping to other approaches.
  • XPath - XPath based mapping.
  • Extensible - Virtual properties defined by the MOXy metadata to provide a way to extend a class without modifying the source.
  • XMLNameTransformer - Customized XML Name Conversions.
  • ElementMappingByAttributeValue - Mapping elements based on the value of an attribute.
  • MetadataRepository - Retrieve and use XML binding definitions from outside your application.