| [ATL] strange OCL behavior [message #660830] |
Mon, 21 March 2011 20:12  |
 Philipp Zech
Messages: 96
Registered: July 2009 |
Member |
|
|
Hi,
I'm currently writing some M2M transformations using ATL. One of the
helpers used during the M2M transformation is supposed to identify
operations with input parameters in the input model, e.g.:
parameters->exists(parameter | parameter.direction = #_in)
however, somehow this statement does not really do what it is supposed
to do, put another way, although the model contains operations with
input parameters, none of the is found. however, if I change "_in" to
"return", e.g.:
parameters->exists(parameter | parameter.direction = #return)
it suddenly works. So, my question, am I wrong in using "_in"?
Considering the OCL documentation it states explicitly that if there may
be ambiguities, as it would be with the word "in", if used in a query
and not as a keyword, and underscore has to be placed directly in front
of the ambiguous word, for that the proper meaning is derived, in this
case the meaning of the parameter direction kind (in) and not the OCL
keyword in. So again my question, what am I doing wrong that no
operation is found?
Thanks,
Philipp
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02596 seconds
Search
Help
Register
Login
Home
