Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 367523

Summary:	[pivot] Unify UML bounded collections with OCL nested collections
Product:	[Modeling] OCL	Reporter:	Ed Willink <ed>
Component:	Core	Assignee:	OCL Inbox <mdt-ocl-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	klaas.gadeyne
Version:	3.2.0
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Ed Willink

2011-12-23 16:38:57 EST

OCL has no support for bounded collections: add upper/lower to Collection.

This then eliminates the need for multiplicities and all the bug opportunities from failing to convert types to collections.

This also requires the Concrete Syntaxes to be revised, which can solve the problem whereby the lack of a multiplicity means that derived Complete OCL properties cannot be optional.

Comment 1 Ed Willink

2012-01-05 01:42:10 EST

From Bug 356243, the following OCLinEcore

property is_always_typed : Classifier<String> { ordered };

fails to parse since arbitrary type references are not allowed; not even Set(String).

Comment 2 Ed Willink

2012-01-30 01:57:27 EST

(In reply to comment #1)
> fails to parse since arbitrary type references are not allowed; not even
> Set(String).

I just tried to use OCLinECore using Complete OCL type syntax; very confusing.

Must add support for Sequence(String) etc.

Comment 3 Ed Willink

2012-08-30 13:15:46 EDT

The pivot model now uses bounded collections and there is a concrete syntax.

Needs more testing.