Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc)  » API Changes in EMFT OCL This Week
API Changes in EMFT OCL This Week [message #573473] Tue, 04 April 2006 13:45
Eclipse UserFriend
Originally posted by: cdamus.ca.ibm.com

Hi, all,

This week's integration build of OCL will have a number of API changes for
the implementation of the OMG's OCL 2.0 Adopted Specification. These
include:

- restructuring of the AST model to account for changes in the OCL spec
to align with UML 2.0. e.g., AttributeCallExp and AssociationEndCallExp
are merged as a single PropertyCallExp type

- changed Visitor methods to adapt to the AST model changes

- new Visitor methods to handle new AST constructs, such as StateExp,
MessageExp, TypeExp. These are also implemented by the
AbstractVisitorImpl class

- the ocl.uml package no longer models UML constructs such as Signal,
Operation, and AssociationClass. The parser now uses the Environment
interface to query for UML aspects of Ecore elements

- new EnvironmentFactory methods for creating Environments on a Property
context (to support init: and derive: expressions)

- new Environment methods to support property context and the UML
constructs not implemented by Ecore

Other changes include:

- the IOCLHelper and ExpressionsUtil convenience APIs support expressions
in property context, such as init: and derive:

- IOCLHelper and ExpressionsUtil add define() methods to define additional
properties and operations (def: expressions)

- EvaluationEnvironment supports the evaluation of expressions using
additional (def:) properties and operations

If you only use the IOCLHelper/ExpressionsUtil/Query APIs for parsing and
evaluating OCL expressions, you should not be affected by these changes
(except for ExpressionsUtil no longer throwing ANTLR exceptions; see
below). If you work with the AST or provide custom Environments, then
these changes are significant but quite straight-forward to adopt.

Finally, this week's build will remove the dependency on the ANTLR parser
generator and the awkward installation procedure. It uses instead a
bottom-up parser from the LALR Parser Generator project in SourceForge.

Cheers,

Christian
Previous Topic:CDO Editor now read/write
Next Topic:Closure + ClosureAll operation
Goto Forum:
  


Current Time: Wed May 22 14:51:15 GMT 2024

Powered by FUDForum. Page generated in 0.02448 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top