Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » M2M (model-to-model transformation) » [ATL] Re: feature e does not exist on
[ATL] Re: feature e does not exist on [message #46058] Wed, 13 June 2007 15:08 Go to next message
Eclipse UserFriend
Originally posted by: marcos.didonet-del-fabro.univ-nantes.fr

Hello,

this usually happens when the helper is not defined, but this is not your case..

Another question, which model handler are you using? AMW or EMF?


Regards,

Marcos.


ps.: I am copying this message to the ATL newsgroup, maybe somebody can help.


kornev wrote:
> Hi Marcos,
> i am using the ATL launch configuration
>
> structurebase ->MOF
> IN->AMW
> interbase ->MOF
> advice ->MOF
>
> structurebase ->structureBase.ecore
> interbase ->interBase.ecore
> advice ->interaction.ecore
> MOF ->#EMF
> IN ->test.ecore
> AMW ->w_model.ecore
>
> so, structurebase, interbase and advice are metamodels that conform to
> Ecore
>
> best regards,
> Yuri
> Marcos Didonet Del Fabro schrieb:
>> Hi, how are you executing the transformation? Using the AMW main
>> plug-in or using the ATL launch configuration?
>>
>>
>> Marcos.
>>
>> kornev wrote:
>>> Hi,
>>>
>>> i tried to define some transformation rules with Atl and was stumbled
>>> on the following:
>>> (exerpt)
>>> module CPMMWeave;
>>> create OUT : MOF from IN : AMW, interbase: MOF, structurebase: MOF,
>>> advice : MOF;
>>>
>>> helper context MOF!EModelElement def: isStBase : Boolean =
>>> MOF!EModelElement.allInstancesFrom ('structurebase')-> exists(e | e =
>>> self );
>>>
>>> rule CopyStClass {
>>> from
>>> be : MOF!EClass (be.isStBase)
>>> to
>>> out : MOF!EClass (
>>> name <- be.name,
>>> )
>>> }
>>> if i run this littel fragment i get
>>> ****** BEGIN Stack Trace
>>> message: feature isStBase does not exist on interbase!EClass
>>> A.main() : ??#32 null
>>> local variables = {self=CPMMWeave : ASMModule}
>>> local stack = []
>>> A.__matcher__() : ??#1 null
>>> local variables = {self=CPMMWeave : ASMModule}
>>> local stack = []
>>> A.__matchCopyBaseInteractionClass() : ??#31 23:34-23:45
>>> local variables = {be=interbase!EClass, self=CPMMWeave : ASMModule}
>>> local stack = []
>>> ****** END Stack Trace
>>>
>>> has someone any idea why this is happing,
>>> i run other examples found on the homepage in works fine,
>>> but here i do not understand, why Atl does not recognize that
>>> interbase conforms to the MOF(Ecore) model and cannot apply isStBase
>>> rule?
Re: [ATL] Re: feature e does not exist on [message #46091 is a reply to message #46058] Wed, 13 June 2007 15:20 Go to previous messageGo to next message
Frédéric Jouault is currently offline Frédéric JouaultFriend
Messages: 572
Registered: July 2009
Senior Member
Hello,

Could you please try to change your attribute helper to an operation
helper (by adding () after its name in its definition usages). It may
help diagnosing the issue.


Regards,

Frédéric Jouault


Marcos Didonet Del Fabro wrote:
> Hello,
>
> this usually happens when the helper is not defined, but this is not
> your case..
>
> Another question, which model handler are you using? AMW or EMF?
>
>
> Regards,
>
> Marcos.
>
>
> ps.: I am copying this message to the ATL newsgroup, maybe somebody can
> help.
>
>
> kornev wrote:
>> Hi Marcos,
>> i am using the ATL launch configuration
>>
>> structurebase ->MOF
>> IN->AMW
>> interbase ->MOF
>> advice ->MOF
>>
>> structurebase ->structureBase.ecore
>> interbase ->interBase.ecore
>> advice ->interaction.ecore
>> MOF ->#EMF
>> IN ->test.ecore
>> AMW ->w_model.ecore
>>
>> so, structurebase, interbase and advice are metamodels that conform to
>> Ecore
>>
>> best regards,
>> Yuri
>> Marcos Didonet Del Fabro schrieb:
>>> Hi, how are you executing the transformation? Using the AMW main
>>> plug-in or using the ATL launch configuration?
>>>
>>>
>>> Marcos.
>>>
>>> kornev wrote:
>>>> Hi,
>>>>
>>>> i tried to define some transformation rules with Atl and was
>>>> stumbled on the following:
>>>> (exerpt)
>>>> module CPMMWeave;
>>>> create OUT : MOF from IN : AMW, interbase: MOF, structurebase: MOF,
>>>> advice : MOF;
>>>>
>>>> helper context MOF!EModelElement def: isStBase : Boolean =
>>>> MOF!EModelElement.allInstancesFrom ('structurebase')-> exists(e | e
>>>> = self );
>>>>
>>>> rule CopyStClass {
>>>> from
>>>> be : MOF!EClass (be.isStBase)
>>>> to
>>>> out : MOF!EClass (
>>>> name <- be.name,
>>>> )
>>>> }
>>>> if i run this littel fragment i get
>>>> ****** BEGIN Stack Trace
>>>> message: feature isStBase does not exist on interbase!EClass
>>>> A.main() : ??#32 null
>>>> local variables = {self=CPMMWeave : ASMModule}
>>>> local stack = []
>>>> A.__matcher__() : ??#1 null
>>>> local variables = {self=CPMMWeave : ASMModule}
>>>> local stack = []
>>>> A.__matchCopyBaseInteractionClass() : ??#31 23:34-23:45
>>>> local variables = {be=interbase!EClass, self=CPMMWeave : ASMModule}
>>>> local stack = []
>>>> ****** END Stack Trace
>>>>
>>>> has someone any idea why this is happing,
>>>> i run other examples found on the homepage in works fine,
>>>> but here i do not understand, why Atl does not recognize that
>>>> interbase conforms to the MOF(Ecore) model and cannot apply isStBase
>>>> rule?
Re: [ATL] Re: feature e does not exist on [message #46122 is a reply to message #46058] Wed, 13 June 2007 15:40 Go to previous messageGo to next message
Yury Kornev is currently offline Yury KornevFriend
Messages: 8
Registered: July 2009
Junior Member
i am using EMF model handler

Marcos Didonet Del Fabro schrieb:
> Hello,
>
> this usually happens when the helper is not defined, but this is not
> your case..
>
> Another question, which model handler are you using? AMW or EMF?
>
>
> Regards,
>
> Marcos.
>
>
> ps.: I am copying this message to the ATL newsgroup, maybe somebody can
> help.
>
>
> kornev wrote:
>> Hi Marcos,
>> i am using the ATL launch configuration
>>
>> structurebase ->MOF
>> IN->AMW
>> interbase ->MOF
>> advice ->MOF
>>
>> structurebase ->structureBase.ecore
>> interbase ->interBase.ecore
>> advice ->interaction.ecore
>> MOF ->#EMF
>> IN ->test.ecore
>> AMW ->w_model.ecore
>>
>> so, structurebase, interbase and advice are metamodels that conform to
>> Ecore
>>
>> best regards,
>> Yuri
>> Marcos Didonet Del Fabro schrieb:
>>> Hi, how are you executing the transformation? Using the AMW main
>>> plug-in or using the ATL launch configuration?
>>>
>>>
>>> Marcos.
>>>
>>> kornev wrote:
>>>> Hi,
>>>>
>>>> i tried to define some transformation rules with Atl and was
>>>> stumbled on the following:
>>>> (exerpt)
>>>> module CPMMWeave;
>>>> create OUT : MOF from IN : AMW, interbase: MOF, structurebase: MOF,
>>>> advice : MOF;
>>>>
>>>> helper context MOF!EModelElement def: isStBase : Boolean =
>>>> MOF!EModelElement.allInstancesFrom ('structurebase')-> exists(e | e
>>>> = self );
>>>>
>>>> rule CopyStClass {
>>>> from
>>>> be : MOF!EClass (be.isStBase)
>>>> to
>>>> out : MOF!EClass (
>>>> name <- be.name,
>>>> )
>>>> }
>>>> if i run this littel fragment i get
>>>> ****** BEGIN Stack Trace
>>>> message: feature isStBase does not exist on interbase!EClass
>>>> A.main() : ??#32 null
>>>> local variables = {self=CPMMWeave : ASMModule}
>>>> local stack = []
>>>> A.__matcher__() : ??#1 null
>>>> local variables = {self=CPMMWeave : ASMModule}
>>>> local stack = []
>>>> A.__matchCopyBaseInteractionClass() : ??#31 23:34-23:45
>>>> local variables = {be=interbase!EClass, self=CPMMWeave : ASMModule}
>>>> local stack = []
>>>> ****** END Stack Trace
>>>>
>>>> has someone any idea why this is happing,
>>>> i run other examples found on the homepage in works fine,
>>>> but here i do not understand, why Atl does not recognize that
>>>> interbase conforms to the MOF(Ecore) model and cannot apply isStBase
>>>> rule?
Re: [ATL] Re: feature e does not exist on [message #46152 is a reply to message #46091] Wed, 13 June 2007 15:49 Go to previous messageGo to next message
Yury Kornev is currently offline Yury KornevFriend
Messages: 8
Registered: July 2009
Junior Member
Hi Frédéric,

i did how you sad this is the console output

Dumping ASM to C:/workspace/emf/ModeWeaving2/CPMMWeave.asm
****** BEGIN Stack Trace
message: ERROR: could not find operation isStBase on interbase!EClass
having supertypes: [interbase!EClassifier, OclType, OclAny] (including
Java operations)
A.main() : ??#26 null
local variables = {self=CPMMWeave : ASMModule}
local stack = []
A.__matcher__() : ??#1 null
local variables = {self=CPMMWeave : ASMModule}
local stack = []
A.__matchCopyBaseInteractionClass() : ??#31 23:34-23:47
local variables = {be=interbase!EClass, self=CPMMWeave : ASMModule}
local stack = []
****** END Stack Trace
Execution terminated due to error (see launch configuration to allow
continuation after errors).

Frédéric Jouault schrieb:
> Hello,
>
> Could you please try to change your attribute helper to an operation
> helper (by adding () after its name in its definition usages). It may
> help diagnosing the issue.
>
>
> Regards,
>
> Frédéric Jouault
>
>
> Marcos Didonet Del Fabro wrote:
>> Hello,
>>
>> this usually happens when the helper is not defined, but this is not
>> your case..
>>
>> Another question, which model handler are you using? AMW or EMF?
>>
>>
>> Regards,
>>
>> Marcos.
>>
>>
>> ps.: I am copying this message to the ATL newsgroup, maybe somebody
>> can help.
>>
>>
>> kornev wrote:
>>> Hi Marcos,
>>> i am using the ATL launch configuration
>>>
>>> structurebase ->MOF
>>> IN->AMW
>>> interbase ->MOF
>>> advice ->MOF
>>>
>>> structurebase ->structureBase.ecore
>>> interbase ->interBase.ecore
>>> advice ->interaction.ecore
>>> MOF ->#EMF
>>> IN ->test.ecore
>>> AMW ->w_model.ecore
>>>
>>> so, structurebase, interbase and advice are metamodels that conform
>>> to Ecore
>>>
>>> best regards,
>>> Yuri
>>> Marcos Didonet Del Fabro schrieb:
>>>> Hi, how are you executing the transformation? Using the AMW main
>>>> plug-in or using the ATL launch configuration?
>>>>
>>>>
>>>> Marcos.
>>>>
>>>> kornev wrote:
>>>>> Hi,
>>>>>
>>>>> i tried to define some transformation rules with Atl and was
>>>>> stumbled on the following:
>>>>> (exerpt)
>>>>> module CPMMWeave;
>>>>> create OUT : MOF from IN : AMW, interbase: MOF, structurebase: MOF,
>>>>> advice : MOF;
>>>>>
>>>>> helper context MOF!EModelElement def: isStBase : Boolean =
>>>>> MOF!EModelElement.allInstancesFrom ('structurebase')-> exists(e | e
>>>>> = self );
>>>>>
>>>>> rule CopyStClass {
>>>>> from
>>>>> be : MOF!EClass (be.isStBase)
>>>>> to
>>>>> out : MOF!EClass (
>>>>> name <- be.name,
>>>>> )
>>>>> }
>>>>> if i run this littel fragment i get
>>>>> ****** BEGIN Stack Trace
>>>>> message: feature isStBase does not exist on interbase!EClass
>>>>> A.main() : ??#32 null
>>>>> local variables = {self=CPMMWeave : ASMModule}
>>>>> local stack = []
>>>>> A.__matcher__() : ??#1 null
>>>>> local variables = {self=CPMMWeave : ASMModule}
>>>>> local stack = []
>>>>> A.__matchCopyBaseInteractionClass() : ??#31 23:34-23:45
>>>>> local variables = {be=interbase!EClass, self=CPMMWeave :
>>>>> ASMModule}
>>>>> local stack = []
>>>>> ****** END Stack Trace
>>>>>
>>>>> has someone any idea why this is happing,
>>>>> i run other examples found on the homepage in works fine,
>>>>> but here i do not understand, why Atl does not recognize that
>>>>> interbase conforms to the MOF(Ecore) model and cannot apply
>>>>> isStBase rule?
Re: [ATL] Re: feature e does not exist on [message #46182 is a reply to message #46091] Wed, 13 June 2007 15:56 Go to previous messageGo to next message
Yury Kornev is currently offline Yury KornevFriend
Messages: 8
Registered: July 2009
Junior Member
i thought maybe it can be the reason:
in my metamodels one metamodel(structurebase) has references to the
elements of the other one (interbase)?

Frédéric Jouault schrieb:
> Hello,
>
> Could you please try to change your attribute helper to an operation
> helper (by adding () after its name in its definition usages). It may
> help diagnosing the issue.
>
>
> Regards,
>
> Frédéric Jouault
>
>
> Marcos Didonet Del Fabro wrote:
>> Hello,
>>
>> this usually happens when the helper is not defined, but this is not
>> your case..
>>
>> Another question, which model handler are you using? AMW or EMF?
>>
>>
>> Regards,
>>
>> Marcos.
>>
>>
>> ps.: I am copying this message to the ATL newsgroup, maybe somebody
>> can help.
>>
>>
>> kornev wrote:
>>> Hi Marcos,
>>> i am using the ATL launch configuration
>>>
>>> structurebase ->MOF
>>> IN->AMW
>>> interbase ->MOF
>>> advice ->MOF
>>>
>>> structurebase ->structureBase.ecore
>>> interbase ->interBase.ecore
>>> advice ->interaction.ecore
>>> MOF ->#EMF
>>> IN ->test.ecore
>>> AMW ->w_model.ecore
>>>
>>> so, structurebase, interbase and advice are metamodels that conform
>>> to Ecore
>>>
>>> best regards,
>>> Yuri
>>> Marcos Didonet Del Fabro schrieb:
>>>> Hi, how are you executing the transformation? Using the AMW main
>>>> plug-in or using the ATL launch configuration?
>>>>
>>>>
>>>> Marcos.
>>>>
>>>> kornev wrote:
>>>>> Hi,
>>>>>
>>>>> i tried to define some transformation rules with Atl and was
>>>>> stumbled on the following:
>>>>> (exerpt)
>>>>> module CPMMWeave;
>>>>> create OUT : MOF from IN : AMW, interbase: MOF, structurebase: MOF,
>>>>> advice : MOF;
>>>>>
>>>>> helper context MOF!EModelElement def: isStBase : Boolean =
>>>>> MOF!EModelElement.allInstancesFrom ('structurebase')-> exists(e | e
>>>>> = self );
>>>>>
>>>>> rule CopyStClass {
>>>>> from
>>>>> be : MOF!EClass (be.isStBase)
>>>>> to
>>>>> out : MOF!EClass (
>>>>> name <- be.name,
>>>>> )
>>>>> }
>>>>> if i run this littel fragment i get
>>>>> ****** BEGIN Stack Trace
>>>>> message: feature isStBase does not exist on interbase!EClass
>>>>> A.main() : ??#32 null
>>>>> local variables = {self=CPMMWeave : ASMModule}
>>>>> local stack = []
>>>>> A.__matcher__() : ??#1 null
>>>>> local variables = {self=CPMMWeave : ASMModule}
>>>>> local stack = []
>>>>> A.__matchCopyBaseInteractionClass() : ??#31 23:34-23:45
>>>>> local variables = {be=interbase!EClass, self=CPMMWeave :
>>>>> ASMModule}
>>>>> local stack = []
>>>>> ****** END Stack Trace
>>>>>
>>>>> has someone any idea why this is happing,
>>>>> i run other examples found on the homepage in works fine,
>>>>> but here i do not understand, why Atl does not recognize that
>>>>> interbase conforms to the MOF(Ecore) model and cannot apply
>>>>> isStBase rule?
Re: [ATL] Re: feature e does not exist on [message #46242 is a reply to message #46182] Wed, 13 June 2007 16:15 Go to previous messageGo to next message
Frédéric Jouault is currently offline Frédéric JouaultFriend
Messages: 572
Registered: July 2009
Senior Member
Hello,

I do not see where your problem is.

Do you have it committed on some CVS or SVN repository?
Or else, could you package your project (with all necessary files,
including launch configurations or ant scripts) in a zip file?


Best regards,

Frédéric Jouault


kornev wrote:
> i thought maybe it can be the reason:
> in my metamodels one metamodel(structurebase) has references to the
> elements of the other one (interbase)?
>
> Frédéric Jouault schrieb:
>> Hello,
>>
>> Could you please try to change your attribute helper to an operation
>> helper (by adding () after its name in its definition usages). It may
>> help diagnosing the issue.
>>
>>
>> Regards,
>>
>> Frédéric Jouault
>>
>>
>> Marcos Didonet Del Fabro wrote:
>>> Hello,
>>>
>>> this usually happens when the helper is not defined, but this is not
>>> your case..
>>>
>>> Another question, which model handler are you using? AMW or EMF?
>>>
>>>
>>> Regards,
>>>
>>> Marcos.
>>>
>>>
>>> ps.: I am copying this message to the ATL newsgroup, maybe somebody
>>> can help.
>>>
>>>
>>> kornev wrote:
>>>> Hi Marcos,
>>>> i am using the ATL launch configuration
>>>>
>>>> structurebase ->MOF
>>>> IN->AMW
>>>> interbase ->MOF
>>>> advice ->MOF
>>>>
>>>> structurebase ->structureBase.ecore
>>>> interbase ->interBase.ecore
>>>> advice ->interaction.ecore
>>>> MOF ->#EMF
>>>> IN ->test.ecore
>>>> AMW ->w_model.ecore
>>>>
>>>> so, structurebase, interbase and advice are metamodels that conform
>>>> to Ecore
>>>>
>>>> best regards,
>>>> Yuri
>>>> Marcos Didonet Del Fabro schrieb:
>>>>> Hi, how are you executing the transformation? Using the AMW main
>>>>> plug-in or using the ATL launch configuration?
>>>>>
>>>>>
>>>>> Marcos.
>>>>>
>>>>> kornev wrote:
>>>>>> Hi,
>>>>>>
>>>>>> i tried to define some transformation rules with Atl and was
>>>>>> stumbled on the following:
>>>>>> (exerpt)
>>>>>> module CPMMWeave;
>>>>>> create OUT : MOF from IN : AMW, interbase: MOF, structurebase:
>>>>>> MOF, advice : MOF;
>>>>>>
>>>>>> helper context MOF!EModelElement def: isStBase : Boolean =
>>>>>> MOF!EModelElement.allInstancesFrom ('structurebase')-> exists(e |
>>>>>> e = self );
>>>>>>
>>>>>> rule CopyStClass {
>>>>>> from
>>>>>> be : MOF!EClass (be.isStBase)
>>>>>> to
>>>>>> out : MOF!EClass (
>>>>>> name <- be.name,
>>>>>> )
>>>>>> }
>>>>>> if i run this littel fragment i get
>>>>>> ****** BEGIN Stack Trace
>>>>>> message: feature isStBase does not exist on interbase!EClass
>>>>>> A.main() : ??#32 null
>>>>>> local variables = {self=CPMMWeave : ASMModule}
>>>>>> local stack = []
>>>>>> A.__matcher__() : ??#1 null
>>>>>> local variables = {self=CPMMWeave : ASMModule}
>>>>>> local stack = []
>>>>>> A.__matchCopyBaseInteractionClass() : ??#31 23:34-23:45
>>>>>> local variables = {be=interbase!EClass, self=CPMMWeave :
>>>>>> ASMModule}
>>>>>> local stack = []
>>>>>> ****** END Stack Trace
>>>>>>
>>>>>> has someone any idea why this is happing,
>>>>>> i run other examples found on the homepage in works fine,
>>>>>> but here i do not understand, why Atl does not recognize that
>>>>>> interbase conforms to the MOF(Ecore) model and cannot apply
>>>>>> isStBase rule?
Re: [ATL] Re: feature e does not exist on [message #46271 is a reply to message #46242] Wed, 13 June 2007 18:20 Go to previous messageGo to next message
Yury Kornev is currently offline Yury KornevFriend
Messages: 8
Registered: July 2009
Junior Member
hi Frédéric,

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?

best regards,
yuri

Frédéric Jouault schrieb:
> Hello,
>
> I do not see where your problem is.
>
> Do you have it committed on some CVS or SVN repository?
> Or else, could you package your project (with all necessary files,
> including launch configurations or ant scripts) in a zip file?
>
>
> Best regards,
>
> Frédéric Jouault
>
>
> kornev wrote:
>> i thought maybe it can be the reason:
>> in my metamodels one metamodel(structurebase) has references to the
>> elements of the other one (interbase)?
>>
>> Frédéric Jouault schrieb:
>>> Hello,
>>>
>>> Could you please try to change your attribute helper to an operation
>>> helper (by adding () after its name in its definition usages). It may
>>> help diagnosing the issue.
>>>
>>>
>>> Regards,
>>>
>>> Frédéric Jouault
>>>
>>>
>>> Marcos Didonet Del Fabro wrote:
>>>> Hello,
>>>>
>>>> this usually happens when the helper is not defined, but this is not
>>>> your case..
>>>>
>>>> Another question, which model handler are you using? AMW or EMF?
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Marcos.
>>>>
>>>>
>>>> ps.: I am copying this message to the ATL newsgroup, maybe somebody
>>>> can help.
>>>>
>>>>
>>>> kornev wrote:
>>>>> Hi Marcos,
>>>>> i am using the ATL launch configuration
>>>>>
>>>>> structurebase ->MOF
>>>>> IN->AMW
>>>>> interbase ->MOF
>>>>> advice ->MOF
>>>>>
>>>>> structurebase ->structureBase.ecore
>>>>> interbase ->interBase.ecore
>>>>> advice ->interaction.ecore
>>>>> MOF ->#EMF
>>>>> IN ->test.ecore
>>>>> AMW ->w_model.ecore
>>>>>
>>>>> so, structurebase, interbase and advice are metamodels that conform
>>>>> to Ecore
>>>>>
>>>>> best regards,
>>>>> Yuri
>>>>> Marcos Didonet Del Fabro schrieb:
>>>>>> Hi, how are you executing the transformation? Using the AMW main
>>>>>> plug-in or using the ATL launch configuration?
>>>>>>
>>>>>>
>>>>>> Marcos.
>>>>>>
>>>>>> kornev wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> i tried to define some transformation rules with Atl and was
>>>>>>> stumbled on the following:
>>>>>>> (exerpt)
>>>>>>> module CPMMWeave;
>>>>>>> create OUT : MOF from IN : AMW, interbase: MOF, structurebase:
>>>>>>> MOF, advice : MOF;
>>>>>>>
>>>>>>> helper context MOF!EModelElement def: isStBase : Boolean =
>>>>>>> MOF!EModelElement.allInstancesFrom ('structurebase')-> exists(e |
>>>>>>> e = self );
>>>>>>>
>>>>>>> rule CopyStClass {
>>>>>>> from
>>>>>>> be : MOF!EClass (be.isStBase)
>>>>>>> to
>>>>>>> out : MOF!EClass (
>>>>>>> name <- be.name,
>>>>>>> )
>>>>>>> }
>>>>>>> if i run this littel fragment i get
>>>>>>> ****** BEGIN Stack Trace
>>>>>>> message: feature isStBase does not exist on interbase!EClass
>>>>>>> A.main() : ??#32 null
>>>>>>> local variables = {self=CPMMWeave : ASMModule}
>>>>>>> local stack = []
>>>>>>> A.__matcher__() : ??#1 null
>>>>>>> local variables = {self=CPMMWeave : ASMModule}
>>>>>>> local stack = []
>>>>>>> A.__matchCopyBaseInteractionClass() : ??#31 23:34-23:45
>>>>>>> local variables = {be=interbase!EClass, self=CPMMWeave :
>>>>>>> ASMModule}
>>>>>>> local stack = []
>>>>>>> ****** END Stack Trace
>>>>>>>
>>>>>>> has someone any idea why this is happing,
>>>>>>> i run other examples found on the homepage in works fine,
>>>>>>> but here i do not understand, why Atl does not recognize that
>>>>>>> interbase conforms to the MOF(Ecore) model and cannot apply
>>>>>>> isStBase rule?
Re: [ATL] Re: feature e does not exist on [message #46301 is a reply to message #46271] Wed, 13 June 2007 19:06 Go to previous messageGo to next message
Frédéric Jouault is currently offline Frédéric JouaultFriend
Messages: 572
Registered: July 2009
Senior Member
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
Re: [ATL] Re: feature e does not exist on [message #46331 is a reply to message #46301] Wed, 13 June 2007 19:42 Go to previous messageGo to next message
Yury Kornev is currently offline Yury KornevFriend
Messages: 8
Registered: July 2009
Junior Member
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
Re: [ATL] Re: feature e does not exist on [message #47462 is a reply to message #46331] Tue, 19 June 2007 11:19 Go to previous messageGo to next message
Dennis Wagelaar is currently offline Dennis WagelaarFriend
Messages: 147
Registered: July 2009
Senior Member
I cannot reproduce this issue. I use ATL on a similar metamodel without
issues:

http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML2CaseStudies/uml 2cs-instantmessenger-config/model/InstantMessenger.ecore?vie w=markup

http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML2CaseStudies/uml 2cs-instantmessenger-config-editor/src/be/ac/vub/uml2cs/inst antmessenger/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=advan ced&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
Re: [ATL] Re: feature e does not exist on [message #54879 is a reply to message #47462] Thu, 26 July 2007 11:36 Go to previous messageGo to next message
Yury Kornev is currently offline Yury KornevFriend
Messages: 8
Registered: July 2009
Junior Member
hi,
so i got this response

------- Comment #1 from mikael.barbero@univ-nantes.fr 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".


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/uml 2cs-instantmessenger-config/model/InstantMessenger.ecore?vie w=markup
>
>
> http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML2CaseStudies/uml 2cs-instantmessenger-config-editor/src/be/ac/vub/uml2cs/inst antmessenger/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=advan ced&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
Re: [ATL] Re: feature e does not exist on [message #54960 is a reply to message #54879] Thu, 26 July 2007 12:30 Go to previous message
Dennis Wagelaar is currently offline Dennis WagelaarFriend
Messages: 147
Registered: July 2009
Senior Member
kornev schreef:
> hi,
> so i got this response

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

>
> ------- Comment #1 from mikael.barbero@univ-nantes.fr 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/uml 2cs-instantmessenger-config/model/InstantMessenger.ecore?vie w=markup
>>
>>
>> http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML2CaseStudies/uml 2cs-instantmessenger-config-editor/src/be/ac/vub/uml2cs/inst antmessenger/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=advan ced&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
Previous Topic:[ATL]problem in something2XML transformation
Next Topic:[ATL] transformations with multiple input metamodels/libraries failing from Java
Goto Forum:
  


Current Time: Mon Jan 18 08:52:05 GMT 2021

Powered by FUDForum. Page generated in 0.02331 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top