[news.eclipse.tools.emf] Re: Interdependency of EMF models

[Ed Merks <Ed.Merks@xxxxxxxxx>]

Kai,

Comments below.


Kai Schlamp wrote:
> It is possible, but not at first time setup. One has to create model A 
> without any dependeny and create the Genmodel for A. Now create model 
> B with dependeny to A and generate the Genmodel for B (with 
> referencing the A Genmodel). Now add to model A new references to 
> model B and reload the genmodel of A (with referencing Genmodel B).
I see.  I suppose when you Reload... A it allows you to reference B but 
really it should require B to be in the same GenModel.  It sounds like 
we need to add some more smarts to the wizard so that mutually dependent 
models can't be split this way...
> This works without any error or warning info.
>
> As I see it is possible to have two Ecore files for one Genmodel. Or 
> to have one Ecore (with subpackages) for one Genmodel.
> Are there any advantages or disadvantages between those both designs?
Generally you should consider that nesting of packages has no meaning.  
They're just separate packages that happen to be nested.  Personally I'd 
avoid nesting packages...
> Ed Merks wrote:
> > Kai,
> >
> > I'm surprised it would let you.  Perhaps you added dependencies after 
> > creating the GenModel and didn't reload it?  Interdependent packages 
> > need to be initialized in an interdependent way and need to be 
> > generated at the same time from a single GenModel....
> >
> >
> > Kai Schlamp wrote:
> > > Hello Ed,
> > >
> > > both are in seperate generator models. When setting up the generator 
> > > model, I add the other package (resp. genmodel) via "Reference 
> > > generator models" in the setup wizard.
> > > So, this won't work?
> > >
> > > Ed Merks wrote:
> > > > Kai,
> > > >
> > > > Interdependency is definitely allowed, as long as both packages are 
> > > > part of a single GenModel.  Any there clues in the Error Log?   
> > > > Feel free to open a bugzilla with a sample that reproduces this 
> > > > inappropriate behavior.