Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329959 - [evaluator] Use oppositeendfinder's ExtentMap for allInstances() implementation
Summary: [evaluator] Use oppositeendfinder's ExtentMap for allInstances() implementation
Status: CLOSED DUPLICATE of bug 251621
Alias: None
Product: OCL
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: OCL Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-10 17:47 EST by Axel Uhl CLA
Modified: 2010-11-13 04:49 EST (History)
1 user (show)

See Also:

Attachments
allInstances() based on ExtentMap from oppositeendfinder (4.52 KB, patch)
2010-11-10 17:47 EST, Axel Uhl CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Uhl CLA 2010-11-10 17:47:03 EST 
Build Identifier: CVS Head of 2010-11-10

This is a follow-up patch for bug 251621 with attachment https://bugs.eclipse.org/bugs/attachment.cgi?id=182851 based on attachment https://bugs.eclipse.org/bugs/attachment.cgi?id=182848. The oppositeendfinder offers scoped allInstances() queries with pluggable scope and an ExtentMap based on this. The patch attached here uses this ExtentMap for allInstances() which makes it consistent with opposite property navigation.

Reproducible: Always
Comment 1 Axel Uhl CLA 2010-11-10 17:47:39 EST 
Created attachment 182857 [details]
allInstances() based on ExtentMap from oppositeendfinder
Comment 2 Ed Willink CLA 2010-11-13 04:49:05 EST 
The contribution is part of Bug 251621. There seems little point in a separate Bugzilla.

*** This bug has been marked as a duplicate of bug 251621 ***