Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 264319 - setCallBack method should be pulled up from XpandExecutionContextImpl to ExecutionContextImpl
Summary: setCallBack method should be pulled up from XpandExecutionContextImpl to Exec...
Status: CLOSED FIXED
Alias: None
Product: M2T
Classification: Modeling
Component: Xpand (show other bugs)
Version: 0.7.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: M6   Edit
Assignee: Arto Laurila CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-10 05:21 EST by Alexander Nyßen CLA
Modified: 2013-02-21 08:09 EST (History)
1 user (show)

See Also:

Attachments
Pull-up patch (2.17 KB, patch)
2009-02-10 06:46 EST, Alexander Nyßen CLA 		sven.efftinge: iplog+
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 Alexander Nyßen CLA 2009-02-10 05:21:56 EST 
As org.openarchitectureware.core.expressions.ExecutionContextImpl does already contain the (protected) callback field, it would be nice to have the setter-method there as well, instead of declaring it in the XpandExecutionContextImpl subclass. This would allow more flexibility when dealing with callbacks, as up to now ExecutionContextImpl does only provide a relatively large constructor as the single opportunity to specify a callback.
Comment 1 Alexander Nyßen CLA 2009-02-10 06:46:14 EST 
Created attachment 125224 [details]
Pull-up patch
Comment 2 Sven Efftinge CLA 2009-02-10 07:02:27 EST 
fixed in HEAD of M2T/Xpand
Comment 3 Patrick Schonbach CLA 2009-02-10 08:36:26 EST 
Also fixed in HEAD of oaW 4.3.1
Comment 4 Karsten Thoms CLA 2013-02-21 08:09:38 EST 
Bug resolved before Xpand 1.2 release date => Closing