Difference between revisions of "VIATRA/Releases/Query/NewAndNoteWorthy1.0"
(add info about pure whitelist) |
(add link to pure whitelist) |
||
| Line 17: | Line 17: | ||
== Whitelist for pure methods == | == Whitelist for pure methods == | ||
| − | If you have a pure method and want to call it in a check()/eval() constraint, you can either annotate it with the <tt>@Pure</tt> annotation of Xbase or register it via the <tt>org.eclipse.incquery.patternlanguage.purewhitelist</tt> extension point. | + | If you have a pure method and want to call it in a check()/eval() constraint, you can either annotate it with the <tt>@Pure</tt> annotation of Xbase or register it via the <tt>org.eclipse.incquery.patternlanguage.purewhitelist</tt> extension point. For more details, refer to the [[EMFIncQuery/UserDocumentation/PureWhitelist|documentation]]. |
Revision as of 09:19, 23 June 2015
Contents
New and Noteworthy - EMF-IncQuery 1.0.0
Surrogate queries for derived features
While query-based features have supported the definition of well-behaving derived features in Ecore models, users of Ecore models that could not be modified had no way for using derived features in queries. EMF-IncQuery 1.0.0 introduces surrogate queries for derived features, where a derived feature in a query is replaced by a subpattern call during runtime. For more details, refer to the documentation.
Enhanced support for UML models
The EMF-UML metamodel contains numerous derived features, most of which can now be used in IncQuery patterns. For more details, refer to the documentation.
Updated Validation Framework
Live validation is not only about Eclipse problem markers any more! The new validation framework provides better expressibility for constraints and a full runtime API with concepts like constraints and violations. To take full advantage of incremental evaluation, users can listen for changes in the validation results. For more details, refer to the documentation.
Updated Viewers Framework
Whitelist for pure methods
If you have a pure method and want to call it in a check()/eval() constraint, you can either annotate it with the @Pure annotation of Xbase or register it via the org.eclipse.incquery.patternlanguage.purewhitelist extension point. For more details, refer to the documentation.