Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347413 - [impact] Impact analyzer doesn't handle derived properties
Summary: [impact] Impact analyzer doesn't handle derived properties
Status: CLOSED FIXED
Alias: None
Product: OCL
Classification: Modeling
Component: Core (show other bugs)
Version: 3.1.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.1.0   Edit
Assignee: OCL Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-27 04:51 EDT by Axel Uhl CLA
Modified: 2011-05-27 06:58 EDT (History)
1 user (show)

See Also:

Attachments
Patch handling derived properties, including tests (31.60 KB, patch)
2011-05-27 05:09 EDT, 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 2011-05-27 04:51:08 EDT 
While the impact analyzer traverses operation calls correctly, it currently doesn't walk derived property definitions provided in OCL.
Comment 1 Axel Uhl CLA 2011-05-27 05:09:27 EDT 
Created attachment 196731 [details]
Patch handling derived properties, including tests

This patch contains an implementation for the TracebackStep (default) approach which can handle derived properties. It extends the o.e.o.examples.impactanalyzer.testmodel.company model by some derived properties which are then used by a few new tests. Note that at least for one test there is a check for the current IA implementation strategy, ensuring the test is only applied for the TracebackStep strategy.

I ran the default and IA tests with this patch with no errors.
Comment 2 Ed Willink CLA 2011-05-27 06:00:02 EDT 
Tests run. Changes small and confined to examples.impact.... +1.
Comment 3 Axel Uhl CLA 2011-05-27 06:58:05 EDT 
Committed to CVS for RC3
Comment 4 Axel Uhl CLA 2011-05-27 06:58:27 EDT 
Closing