|
| Re: Multiple schemas... mixed... multiple versions... [message #529196 is a reply to message #529022] |
Fri, 23 April 2010 10:56  |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Generally you should try to evolve such schemas is a binary compatible
manner. I.e., in a manner that maps the generated API binary
compatible so only add things, don't remove or rename existing things.
The EMF recipes show a data migration recipe for more complex
incompatible changes, but those are best avoided.
tfennelly wrote:
> Hi there.
>
> Apologies if this question has already been asked in some other form.
> I searched the newsgroup archive and goodled but can't seem to find an
> answer.
>
> Anyway... I have an editor which needs to handle a config model that's
> based on a "base" schema + multiple sub-schemas. The sub-schemas are
> evolving over time, but we want the editor to be backward compatible
> with the earlier versions of these schemas. I hope this makes sense.
>
> Is there a best practice for handling this type of use case - multiple
> mixed schemas with support for multiple versions of schema?
>
> Would this require multiple EMF models... one for each version of a
> given schema, or is there a way to support multiple versions of a
> given schema from a single underlying model?
>
> T.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.02819 seconds
] 
Search
Help
Register
Login
Home
