I have the following ideas: 1) Collapse the Context object entirely into the AegisDatabinding. 2) Eliminate the 'multiple type mappings by encoding' business - unless Dain is getting mileage out of it for SOAP.
The idea seems to have been that a mapping XML file could give different mappings for different soap encodings. The code is almost surely not working now, as the CXF integration involved adding a per-service type mapping that seems to usually end up in charge. If we wanted this, I think that we would want a different arrangement. If seems to me that the service can have multiple bindings, each with its own encoding. However, I'd vote for each of these having its own databinding object, and having the databinding store only one type mapping registry.
