search

osate / osate2

Open Source AADL2 Tool Environment
http://osate.org
Eclipse Public License 2.0
36 stars 8 forks source link

Discrepancy between ModeTransition ecore class and Java class #124

Closed dblouin closed 11 years ago

dblouin commented 11 years ago

In the ecore meta-model, the ModeTransition class has a property named ownedTrigger. In the corresponding Java class, the getter is named getOwnedTriggers() with an extra "s". This causes a problem when accessing the property with OCL.

juli1 commented 11 years ago

Hi, Please send patches, this would really helps to keep track the requested changes and the source baseline. Would it be possible to send us a patch regarding this issue ?

dblouin commented 11 years ago

Hi Julien,

Actually, we did not fix this one.

Thanks.

Le 17/11/2012 13:05, Julien a écrit :

Hi, Please send patches, this would really helps to keep track the requested changes and the source baseline. Would it be possible to send us a patch regarding this issue ?

— Reply to this email directly or view it on GitHub https://github.com/osate/osate2-core/issues/124#issuecomment-10473436.

Dominique BLOUIN

Ingénieur de Recherche / Research Engineer

Université de Bretagne Sud Lab-STICC / CNRS UMR 3192

Centre de Recherches BP92116 / 56321 LORIENT Cedex Tel:0297874616 / Fax:0297874527

http://www.labsticc.fr/

juli1 commented 11 years ago

Any help/clue about how to see that as an error ? As we do not use OCL, it would be useful to have a code snippet or a use-case that show this as an error so that we can patch and fix OSATE.

dblouin commented 11 years ago

Actually, I just re-tested it and it seems to be working fine! It seems to be a general rule in the AADL 2 meta-model that an s is added to the collection getters. So I don't exactly know how how it could have been a problem before... Maybe I was trying to call .ownedTriggers in OCL because I had seen the s in the meta-model Java class and was expecting there should be an s in the property name as welll.

Sorry about that.

Le 19/11/2012 17:07, Julien a écrit :

Any help/clue about how to see that as an error ? As we do not use OCL, it would be useful to have a code snippet or a use-case that show this as an error so that we can patch and fix OSATE.

— Reply to this email directly or view it on GitHub https://github.com/osate/osate2-core/issues/124#issuecomment-10519192.

Dominique BLOUIN

Ingénieur de Recherche / Research Engineer

Université de Bretagne Sud Lab-STICC / CNRS UMR 3192

Centre de Recherches BP92116 / 56321 LORIENT Cedex Tel:0297874616 / Fax:0297874527

http://www.labsticc.fr/

juli1 commented 11 years ago

Hi Dominique,

Thanks for letting us know, I assume I can close this ticket now.

Thanks,

Regards,