| Summary: | DefaultReconnectionFeature#reconnect should use getNewAnchor(context) not context.getNewAnchor() | ||
|---|---|---|---|
| Product: | [Modeling] Graphiti | Reporter: | Patrick Talbot <ptalbot> |
| Component: | Core | Assignee: | Michael Wenz <michael.wenz> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | michael.wenz, ptalbot |
| Version: | 0.8.0 | Flags: | michael.wenz:
juno+
|
| Target Milestone: | 0.9.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | Juno M4 Theme_bugs | ||
|
Description
Patrick Talbot
What you intent to do would also be possible by overriding preReconnect and setting the new anchor from there; that would require a cast of the context object from the interface to ReconnectionContext. But, agreed: it's at least asymmetric to call getNewAnchor in canReconnect and to not do it in reconnect. Fixed in head and pushed to Eclipse commit a65599940483e7796cede3453475f85f15252ec5 Author: mwenz <michael.wenz@sap.com> 2011-11-22 16:25:02 Committer: mwenz <michael.wenz@sap.com> 2011-11-22 16:41:23 Parent: 8fd315e42ba4e41a911b39af977be8c7a18a9020 (New images for "Providing Reconnection Functionality") Branches: origin/master, master Bookkeeping: Set target release Part of Graphiti 0.9.0 (Eclipse Juno) |