Eclipse Community Forums: OCL » What is wrong in this expression with enumeration values?

Home » Modeling » OCL » What is wrong in this expression with enumeration values?

What is wrong in this expression with enumeration values? [message #683379]

Mon, 13 June 2011 12:19

Eclipse User

Hi,

I am newbie in OCL. I am working with GMF, and Ecore models, and I am trying to add an Audit Rule with an OCL constraint. This is my constraint:
connector->forAll(r1 | r1.toInPort.logicType = #NO_WAIT implies r1.fromOutPort.logicType = #AND)'

I am getting the follwing error:
Cause: 2:46 "#" unexpected character ignored

logicType attributes are enumerations, what is wrong?

Thank you in advance, regards

Aintzane

(no subject) [message #683405 is a reply to message #683379]

Mon, 13 June 2011 12:54

Eclipse User

Hi

Although # was used in some UML 1.x examples, # was never part of OCL.

You should qualify your enumeration literal with its enumeration e.g.
LogicType::AND.

Where did you find an example suggesting #AND?

Regards

Ed Willink

On 13/06/2011 17:19, Aintzane wrote:
> Hi,
>
> I am newbie in OCL. I am working with GMF, and Ecore models, and I am
> trying to add an Audit Rule with an OCL constraint. This is my
> constraint:
> connector->forAll(r1 | r1.toInPort.logicType = #NO_WAIT implies
> r1.fromOutPort.logicType = #AND)'
>
> I am getting the follwing error:
> Cause: 2:46 "#" unexpected character ignored
>
> logicType attributes are enumerations, what is wrong?
>
> Thank you in advance, regards
>
> Aintzane
>

Re: (no subject) [message #683743 is a reply to message #683405]

Tue, 14 June 2011 06:49

Eclipse User

Hi,

Thank you very much, Edward. Your help has been very useful.

I donwloaded a document called "Object Constraint Language
Specification", but perhaps it is a bit old, from March 2000, I've attached it.

Best regards,

Aintzane

Attachment: Object Constraint Language Specification.pdf
(Size: 275.12KB, Downloaded 1685 times)

Re: (no subject) [message #683922 is a reply to message #683743]

Tue, 14 June 2011 12:16

Eclipse User

Hi

That is a UML 1.3 chapter, so correspomdingly OCL 1.3. Seriously out of
date. Burn it.

The latest specification is at http://www.omg.org/spec/OCL/

Thanks fior the reference,
http://wiki.eclipse.org/MDT/OCL/FAQ#How_do_I_solve:_.22.23.22_unexpected_character_ignored
updated.

Regards

Ed Willink

On 14/06/2011 11:49, Aintzane wrote:
> Hi,
>
> Thank you very much, Edward. Your help has been very useful.
>
> I donwloaded a document called "Object Constraint Language
> Specification", but perhaps it is a bit old, from March 2000, I've attached it.
>
> Best regards,
>
> Aintzane

Re: (no subject) [message #1456159 is a reply to message #683922]

Thu, 30 October 2014 00:32

Eclipse User

Hi,
Sorry for asking this simple question.
I tried to access an Enumeration literal by "EnumerationName::EnumerationLiteralName". Therefore, I have an stereotype ST1, with attribute of Attribute1 which its type is "Enumeration1". I wrote an ocl Like: self.Attribute1=Enumeration1::EnumerationLiteral1.
It gives me java.lang.UnsupportedOperationException.
I am using the nightly version of papyrus. Am I missing something here?

Thanks,
Mahin

Re: (no subject) [message #1456255 is a reply to message #1456159]

Thu, 30 October 2014 02:56

Eclipse User

Hi

This is https://bugs.eclipse.org/bugs/show_bug.cgi?id=448470 for which I
have just developed an interim fix for; just struggling to make the
JUnit test work in conjunction with other plugin tests.

Regards

Ed Willink

On 30/10/2014 05:32, Mahin Abbasipour wrote:
> Hi,
> Sorry for asking this simple question.
> I tried to access an Enumeration literal by
> "EnumerationName::EnumerationLiteralName". Therefore, I have an
> stereotype ST1, with attribute of Attribute1 which its type is
> "Enumeration1". I wrote an ocl Like:
> self.Attribute1=Enumeration1::EnumerationLiteral1.
> It gives me java.lang.UnsupportedOperationException.
> I am using the nightly version of papyrus. Am I missing something here?
>
> Thanks,
> Mahin

Re: (no subject) [message #1457604 is a reply to message #1456255]

Fri, 31 October 2014 09:57

Eclipse User

Hi

Should be fixed in the latest maintenance or nightly version of Eclipse OCL.

http://www.eclipse.org/modeling/download.php?file=/modeling/mdt/ocl/downloads/drops/5.0.3/M201410310813/mdt-ocl-Update-M201410310813.zip

http://www.eclipse.org/modeling/download.php?file=/modeling/mdt/ocl/downloads/drops/5.1.0/N201410310856/mdt-ocl-Update-N201410310856.zip

Regards

Ed Willink

On 30/10/2014 06:56, Ed Willink wrote:
> Hi
>
> This is https://bugs.eclipse.org/bugs/show_bug.cgi?id=448470 for which I
> have just developed an interim fix for; just struggling to make the
> JUnit test work in conjunction with other plugin tests.
>
> Regards
>
> Ed Willink
>
> On 30/10/2014 05:32, Mahin Abbasipour wrote:
>> Hi,
>> Sorry for asking this simple question.
>> I tried to access an Enumeration literal by
>> "EnumerationName::EnumerationLiteralName". Therefore, I have an
>> stereotype ST1, with attribute of Attribute1 which its type is
>> "Enumeration1". I wrote an ocl Like:
>> self.Attribute1=Enumeration1::EnumerationLiteral1.
>> It gives me java.lang.UnsupportedOperationException.
>> I am using the nightly version of papyrus. Am I missing something here?
>>
>> Thanks,
>> Mahin
>

Previous Topic:	Enabling direct OCL-to-Java code generation in Indigo / eclipse 3.7.2
Next Topic:	org.eclipse.jdt.annotation version in RCP product configurations

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 15:14:30 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter