Eclipse Community Forums: OCL » Unresolvable property on class with exactly one association

Help

Home

Home » Modeling » OCL » Unresolvable property on class with exactly one association

Show: Today's Messages :: Show Polls :: Message Navigator

Unresolvable property on class with exactly one association [message #1718838]

Wed, 30 December 2015 23:19

Florian Schneider

Messages: 5
Registered: July 2009

Junior Member

I just downloaded the latest Papyrus and created a very simple class diagram having 2 classes with a 1:1 association, both ends owned by the classifiers.

Then I added a constraint to the diagram and related it to one of the two classes, and set the name of the constraint. I wrote a trivial expression to refer to the association end, but the editor tells me this is an unresolved property (see attached screenshot).

index.php/fa/24452/0/

As soon as I add another property of type String to the class, the error goes away.

Is this a known bug?

Attachment: Screen Shot 2015-12-31 at 00.14.35.png
(Size: 42.80KB, Downloaded 578 times)

Report message to a moderator

Re: Unresolvable property on class with exactly one association [message #1718886 is a reply to message #1718838]

Thu, 31 December 2015 20:50

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

While this isn't exactly a known problem, it's not unknown either.

The incremental refresh of the OCL view of the UML model is manually
coded and probably imperfect. An autogenerated rewrite is underway.

Regards

Ed Willink

On 31/12/2015 16:25, Florian Schneider wrote:
> I just downloaded the latest Papyrus and created a very simple class diagram having 2 classes with a 1:1 association, both ends owned by the classifiers.
>
> Then I added a constraint to the diagram and related it to one of the two classes, and set the name of the constraint. I wrote a trivial expression to refer to the association end, but the editor tells me this is an unresolved property (see attached screenshot).
>
>
>
> As soon as I add another property of type String to the class, the error goes away.
>
> Is this a known bug?

Report message to a moderator

Re: Unresolvable property on class with exactly one association [message #1719115 is a reply to message #1718886]

Tue, 05 January 2016 12:47

Florian Schneider

Messages: 5
Registered: July 2009

Junior Member

I am not convinced that it is a view refresh problem. I can actually close the window, open it again and the error still persists. It only goes away after I added that additional property.

Report message to a moderator

Re: Unresolvable property on class with exactly one association [message #1719153 is a reply to message #1719115]

Tue, 05 January 2016 16:23

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

You are referring to the UI View.

I was referring to the internal Pivot Model that is a view of the UML
model. But closing the editor (not necessarily the same as closing the
window) should force a Pivot Model recreation.

Whatever, it seems like you have a rather small repro. Can you please
post the model and the repro instructions.

Regards

On 05/01/2016 12:47, Florian Schneider wrote:
> I am not convinced that it is a view refresh problem. I can actually
> close the window, open it again and the error still persists. It only
> goes away after I added that additional property.

Report message to a moderator

Re: Unresolvable property on class with exactly one association [message #1719664 is a reply to message #1719153]

Mon, 11 January 2016 08:59

Florian Schneider

Messages: 5
Registered: July 2009

Junior Member

The attached model should contain the error, if it has got nothing to do with plugin or workspace configuration.

The only way I could get rid of the error message has been to create a string property on TestB, string being imported from UML's PrimitiveTypes.

Attachment: model.zip
(Size: 2.79KB, Downloaded 200 times)

Report message to a moderator

Re: Unresolvable property on class with exactly one association [message #1719774 is a reply to message #1719664]

Mon, 11 January 2016 22:45

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

The problem is that your model is 'too simple'. It has no reference to
the UML definition of the UML metamodel. Adding a String property
provides that reference. Most models have an ElementImport or
ProfileApplication.

However, since your model is so simple, OCL probably doesn't need to
know what the UML metamodel is.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=485586

(It is good practice to define a Model.URI property.)

Regards

Ed Willink

On 11/01/2016 08:59, Florian Schneider wrote:
> The attached model should contain the error, if it has got nothing to do with plugin or workspace configuration.
>
> The only way I could get rid of the error message has been to create a string property on TestB, string being imported from UML's PrimitiveTypes.
>
>

Report message to a moderator

Previous Topic:	UML-OCL : Inheriting operations from primitive types in standard UML library
Next Topic:	Extend OCL

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 15:18:11 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter