[xsde-users] Supporting multiple versions of a schema that are not completely backward compatible

Boris Kolpackov boris at codesynthesis.com
Wed Jul 8 12:14:16 EDT 2015

Hi Ravi,

Rangarajan, Ravi_Sowmian <raviraja at qti.qualcomm.com> writes:

> - Is it possible to change name space for say the newer schema
>   so both can co-exist and application code can call respective
>   schema's APIs a run time? If yes, how can I achieve that?

Yes, use the --namespace-map (or --namespace-regex) option.

> - If changing namespace for the newer schema is not possible, then other
>   approach might be to use newer schema alone and whenever an XM file needs
>   to be constructed per old schema, one may have to remove/reset/set few
>   fields to mock old schema, but am not quite sure how to go about those
>   steps needed for the same. Any tips on how to use single schema and mock
>   support for both versions of the schemas?

XSD/e includes support for schema evolution. I am not sure how applicable
it will be to your case, but it may be worth familiarizing yourself with
it; see the examples in the 'evolution' directory.


More information about the xsde-users mailing list