Importing Same Schema, New Version Overwrites Original Messages

Dec 3, 2007 at 2:30 AM
If I import a service as version 1.0 and then change the contracts and import the service again all the 1.0 messages are redefined as the version 1.1 messages. In other words, the 1.0 messages are lost even though there is a 1.0 and 1.1 version of the operations in the catalog. It appears that the schema does not get versioned, so this may causing the problem. I'm not sure what the behavior should be here. I be;ieve that the import should detect that the schema is already imported and warn the user. Perhaps the best practice should be that the schema namespace has to change.
Dec 4, 2007 at 3:45 PM
Yes, if you are trying to import the same namespace, the assumption is that you are replacing the original. However, if you are importing different types, it should add them to the existing namespace. Schema versioning is a big part of the service versioning story and something we will be enhancing (building a bit more intelligence around) in future releases.