[news.eclipse.modeling.gmt.amw] Re: [ATL] Re: feature e does not exist o

[Dennis Wagelaar <dennis.wagelaar@xxxxxxxxx>]

kornev schreef:
> hi,
> so i got this response

Ok, I have some food for thought on that one ;-).

> ------- Comment #1 from mikael.barbero@xxxxxxxxxxxxxx  2007-06-18 05:18 
> -------
> Dear Yuri,
>
> Using Ecore datatypes (i.e. datatypes defined in the metametamodel -- 
> M3) in a
> metamodel -- M2 is not very clean from our point of view. The fact you 
> reuse
> something from the M3 level can be seen as a re-definition of this M3 
> level. It
> doesn't stick with the modeling base principles. Then, we don't planned to
> solve this "bug".

I do not agree ;-)). Using the Ecore *language* can be done on any 
M-level. If I import the Ecore language as part of my own language, then 
that has no effect on the M-level.

I use strings in my meta-model as well as in my model, and the semantics 
of "string" is the same for both M-levels. Hence, I can use the same 
language construct (from the same language). UML goes even further in 
its reuse of Ecore constructs and makes it possible to add EAnnotations 
to all UML elements.

Dennis

> Dennis Wagelaar schrieb:
> > I cannot reproduce this issue. I use ATL on a similar metamodel 
> > without issues:
> >
> > http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML2CaseStudies/uml2cs-instantmessenger-config/model/InstantMessenger.ecore?view=markup 
> >
> >
> > http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML2CaseStudies/uml2cs-instantmessenger-config-editor/src/be/ac/vub/uml2cs/instantmessenger/popup/actions/GenerateBuildFileAction.java?view=markup 
> >
> >
> > If you still experience this issue, please file a bug report: 
> > https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=M2M 
> >
> >
> > Also include the files necessary to reproduce the problem.
> >
> > Regards,
> > Dennis
> >
> > kornev schreef:
> > > Hi,
> > > i'll do it, thanks you and Marcos for help.
> > >
> > > regards,
> > > yuri
> > >
> > > Frédéric Jouault schrieb:
> > > > Hello,
> > > >
> > > >  > i could localize the place where it does not work for me..
> > > >  >
> > > >  > soo the error comes if i use  the reference to the EString 
> > > > -Element in
> > > >  > my models (perhaps some other i did not test jet),
> > > >  > this is the example:
> > > >  >
> > > >  > <?xml version="1.0" encoding="UTF-8"?>
> > > >  > <ecore:EPackage xmi:version="2.0"
> > > >  >     xmlns:xmi="http://www.omg.org/XMI";
> > > >  > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> > > >  >     xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore";
> > > >  > name="StructureBase"
> > > >  >     nsPrefix="">
> > > >  >   <eClassifiers xsi:type="ecore:EClass" name="Cl">
> > > >  >     <eStructuralFeatures xsi:type="ecore:EAttribute" name="name"
> > > >  > eType="ecore:EDataType 
> > > > http://www.eclipse.org/emf/2002/Ecore#//EString"/>
> > > >  >   </eClassifiers>
> > > >  > </ecore:EPackage>
> > > >  >
> > > >  > but if i create my own datatype String instead of using the 
> > > > EString of
> > > >  > Ecore in the main package, the model is transformed without any 
> > > > errors.
> > > >  >
> > > >  > Is it a limitation in ATL or is something wrong with my settings?
> > > >
> > > > ATL should be able to work with this, but you may have found a bug.
> > > > Could you please create a bugzilla entry for it?
> > > >
> > > > Thanks.
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Frédéric Jouault