|
| Re: Steps to update existing sirius VSM odesign after updating it's respective XSD schema [message #1720968 is a reply to message #1719830] |
Fri, 22 January 2016 09:09  |
|
Le 12/01/2016 14:40, rcp menon a écrit :
> Hi,
Hi.
> I have received an odesign file and my requirement is to extend its
> respective XML model by adding one more XML attribute to a specific tag.
> I will be updating respective XSD schema to define this new attribute
> however I am not sure whether I need to regenerate ECore source files
> and re-do all the steps from scratch to regenerate new odesign model. Is
> there a way to solve it without redoing all these activities?
From what I understand, you'll need to regenerate the Ecore and the
corresponding Java sources to match the updated definition of the XSD
schema, but this is independant of Sirius itself, it's just how EMF works.
For the Sirius part (the .odesign here), if you have changed the nsURI
of the Ecore metamodel (for example if it includes a version number and
you have increased it), it may be necessary to update the .odesign if
you had explicitly references your metamodel (in the "Metamodels"
property section of your diagrams/trees/tables definition).
Other than that, changing the .odesign is only needed in so far that you
want your modelers to actually do something with the new attribute. If
you had done more impacting changes (renamed or removed types or
attributes, changed the structure of your models, etc.), of course the
modeler definitions in the .odesign needs to be adjusted so that it can
make sense of the new models' structure.
Regards.
--
Pierre-Charles David - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
Pierre-Charles David - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
Powered by
FUDForum. Page generated in 0.03029 seconds
] 
Search
Help
Register
Login
Home
