eclipse-viatra-bot
commented
6 months ago By Istvan Rath on Apr 01, 2013 05:11
A clarification: these special Java types can be assigned to attributes.
(In reply to comment #0)
Model elements of type Class<? extends something> result in a java.lang.Class
type in the generated evaluateXExpression() method instead of something meaningful. (E.g. "?" or the given type itself.) This causes faulty code (since "T cannot be resolved to a type"). In my particular case the model element is: Class<? extends Event> eventType. But the generated code looks like this: java.lang.Class
eventGuardType = (java.lang.Class )tuple.get(eventGuardTypePosition); Replacing the type parameter with the appropriate one solves the problem, of course. I.e. both -java.lang.Class<?> eventGuardType = (...), and -java.lang.Class<? extends Event> eventGuardType = (...) are OK.
If this is a reasonable behavior (i.e. because of a shortcoming of Xbase, or EMF, etc), it would be nice to mention it in the documentation, or perhaps a warning marker could be placed on the related element in the query.
| --- | --- | | Bugzilla Link | 404652 | | Status | ASSIGNED | | Importance | P3 major | | Reported | Mar 31, 2013 21:59 EDT | | Modified | May 27, 2019 07:45 EDT | | Version | oldinquery | | Reporter | Istvan David |
Description
Model elements of type Class<? extends something> result in a java.lang.Class type in the generated evaluateXExpression() method instead of something meaningful. (E.g. "?" or the given type itself.) This causes faulty code (since "T cannot be resolved to a type").
In my particular case the model element is: Class<? extends Event> eventType.\ But the generated code looks like this:\ java.lang.Class eventGuardType = (java.lang.Class)tuple.get(eventGuardTypePosition);
Replacing the type parameter with the appropriate one solves the problem, of course. I.e. both\ -java.lang.Class<?> eventGuardType = (...), and\ -java.lang.Class<? extends Event> eventGuardType = (...)\ are OK.
If this is a reasonable behavior (i.e. because of a shortcoming of Xbase, or EMF, etc), it would be nice to mention it in the documentation, or perhaps a warning marker could be placed on the related element in the query.