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 #30215] Tue, 04 April 2006 13:45 Go to next message
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
Re: API Changes in EMFT OCL This Week [message #30254 is a reply to message #30215] Tue, 04 April 2006 14:11 Go to previous messageGo to next message
Richard Gronback is currently offline Richard GronbackFriend
Messages: 23
Registered: July 2009
Junior Member
Christian W. Damus wrote:
>
> 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.

Excellent, thanks! :)
Re: API Changes in EMFT OCL This Week [message #30325 is a reply to message #30215] Wed, 05 April 2006 19:31 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: cdamus.ca.ibm.com

These changes are now committed to CVS and will appear, on schedule, in
tomorrow's M6 milestone build.

Cheers,

Christian
Re: API Changes in EMFT OCL This Week [message #30466 is a reply to message #30254] Thu, 06 April 2006 16:55 Go to previous messageGo to next message
Vishy Ramaswamy is currently offline Vishy RamaswamyFriend
Messages: 30
Registered: July 2009
Member
To further clarify
The new M6 OCL build will not require any additional jars to be downloaded.
Everything is self-contained. Just download the OCL component from the
downloads page and you are good to go

Thanks
Vishy
"Richard Gronback" <gronback@acm.org> wrote in message
news:e0tuqc$ic9$1@utils.eclipse.org...
> Christian W. Damus wrote:
> >
> > 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.
>
> Excellent, thanks! :)
Re: API Changes in EMFT OCL This Week [message #30678 is a reply to message #30215] Fri, 07 April 2006 17:28 Go to previous messageGo to next message
Ed Willink is currently offline Ed WillinkFriend
Messages: 7658
Registered: July 2009
Senior Member
> 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:

and also a change of usage from plural to singular, thus LoopExp now
has an "iterator" field (which is a list) rather an "iterators" field.

This seems to be an unfortunate change and is not really consistent with
Ecore which provides plural names for MOF concepts.

Regards

Ed Willink
Re: API Changes in EMFT OCL This Week [message #30821 is a reply to message #30678] Mon, 10 April 2006 22:29 Go to previous message
Eclipse UserFriend
Originally posted by: cdamus.ca.ibm.com

Hi, Ed,

Yes, the names are unfortunate; I never understood why the UML family of
specification chose this singular (in both senses!) naming convention for
multivalued features. Perhaps if/when the OCL and UML2 projects come
together, we can use their fancy code generator to automagically pluralize
the API names.

Cheers,

Christian


Ed Willink wrote:

>> 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:
>
> and also a change of usage from plural to singular, thus LoopExp now
> has an "iterator" field (which is a list) rather an "iterators" field.
>
> This seems to be an unfortunate change and is not really consistent with
> Ecore which provides plural names for MOF concepts.
>
> Regards
>
> Ed Willink
Re: API Changes in EMFT OCL This Week [message #573510 is a reply to message #30215] Tue, 04 April 2006 14:11 Go to previous message
Richard Gronback is currently offline Richard GronbackFriend
Messages: 23
Registered: July 2009
Junior Member
Christian W. Damus wrote:
>
> 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.

Excellent, thanks! :)
Re: API Changes in EMFT OCL This Week [message #573564 is a reply to message #30215] Wed, 05 April 2006 19:31 Go to previous message
Eclipse UserFriend
Originally posted by: cdamus.ca.ibm.com

These changes are now committed to CVS and will appear, on schedule, in
tomorrow's M6 milestone build.

Cheers,

Christian
Re: API Changes in EMFT OCL This Week [message #573681 is a reply to message #30254] Thu, 06 April 2006 16:55 Go to previous message
Vishy Ramaswamy is currently offline Vishy RamaswamyFriend
Messages: 30
Registered: July 2009
Member
To further clarify
The new M6 OCL build will not require any additional jars to be downloaded.
Everything is self-contained. Just download the OCL component from the
downloads page and you are good to go

Thanks
Vishy
"Richard Gronback" <gronback@acm.org> wrote in message
news:e0tuqc$ic9$1@utils.eclipse.org...
> Christian W. Damus wrote:
> >
> > 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.
>
> Excellent, thanks! :)
Re: API Changes in EMFT OCL This Week [message #573948 is a reply to message #30215] Fri, 07 April 2006 17:28 Go to previous message
Ed Willink is currently offline Ed WillinkFriend
Messages: 7658
Registered: July 2009
Senior Member
> 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:

and also a change of usage from plural to singular, thus LoopExp now
has an "iterator" field (which is a list) rather an "iterators" field.

This seems to be an unfortunate change and is not really consistent with
Ecore which provides plural names for MOF concepts.

Regards

Ed Willink
Re: API Changes in EMFT OCL This Week [message #574099 is a reply to message #30678] Mon, 10 April 2006 22:29 Go to previous message
Eclipse UserFriend
Originally posted by: cdamus.ca.ibm.com

Hi, Ed,

Yes, the names are unfortunate; I never understood why the UML family of
specification chose this singular (in both senses!) naming convention for
multivalued features. Perhaps if/when the OCL and UML2 projects come
together, we can use their fancy code generator to automagically pluralize
the API names.

Cheers,

Christian


Ed Willink wrote:

>> 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:
>
> and also a change of usage from plural to singular, thus LoopExp now
> has an "iterator" field (which is a list) rather an "iterators" field.
>
> This seems to be an unfortunate change and is not really consistent with
> Ecore which provides plural names for MOF concepts.
>
> Regards
>
> Ed Willink
Previous Topic:Equality operation contract in OCL expressions?
Next Topic:Equality operation contract in OCL expressions?
Goto Forum:
  


Current Time: Sun May 19 05:33:28 GMT 2024

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

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

Back to the top