Page History

...

Aegis XML mapping applies to services and to beans. By "beans," we mean "Java classes that follow the bean pattern, used in a web service." "Services," you ask? Aren't they the responsibility of the CXF front end? There is some overlap in the responsibilties responsibilities of front-ends and databindings.

By and large, front-ends map services to XML schema, filling in XML Schema elements and the Aegis front end can be used to configure the names and parameters of servicestypes for messages and parts. Data bindings then map from those schema items to Java. However, Aegis also provides XML configuration for methods and parameters, which 'poach' in the territory of the front end. This works well for the Simple front end, which has no other way to control these mappings. The present author is not sure what will happen in the event of a conflict between Aegis and any other front-end, like JAX-WS and Aegis, that has explicit configuration. The Aegis service configuration is best used with the Simple front end.

...

Later on, we will explain how to replace the default mappings that Aegis provides for basic types. However, thre tehre are some cases where you may want to simply specify one of the provided type mappings for one of your properties. You can do that from the XML mapping file without creating any Java customization.

...