|object mapping during evaluation [message #483771]
||Wed, 02 September 2009 17:14
| Elio Damaggio
Registered: July 2009
Thanks everybody for all the previous answers, they have been extremely
The problem I have now is really tricky and I do not know how to solve it.
The deal is this:
1) I have an Ecore object that is not exactly the one I have to perform
the evaluation on. (e.g. some attributes are string instead of dates and
so on, or I have a list of class instances with an attribute a, and it has
to be accessed by OCL as a list of only the "a"). This is clearly a
mapping to be done.
2) Is there a way to hijack the way the OCL parser/evaluator accesses the
properties/types in order to translate these things on the fly?
Any idea is really appreciated...
ps. I have to deal with legacy code and I do not have full control over
it, I know this whole problem should never arise in a clean design... :(