Change Unidirectional Association to Bidirectional

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
(Page Outline Added)
 
m (Reverted edits by Ebybymic (Talk); changed back to last version by Brett Ward)
 
(One intermediate revision by one user not shown)

Latest revision as of 03:11, 25 November 2010

If you have two classes that need to use each other's features, but the link currently goes one way, change the association to bidirectional to allow needed navigation.

This refactoring uses back pointers to implement the needed bidirectionality. This pointer will be added as a field. Decisions will also need to be made on which class controls the association, with the non-controlling side needing a helper method. The existing modifier will need to be altered or added to the controlling side to update the back pointers.

See Also:


Refactoring

Composing Methods: Extract Method | Inline Method | Inline Temp | Replace Temp with Query | Introduce Explaining Variable | Split Temporary Variable | Remove assignments to Parameters | Replace Method with Method Object | Substitute Algorithm
Moving Features Between Objects: Move Method | Move Field | Extract Class | Inline Class | Hide Delegate | Remove Middle Man | Introduce Foreign Method | Introduce Local Extension
Organising Data: Self Encapsulate Field | Replace Data Value with Object | Change Value to Reference | Change Reference to Value | Replace Array with Object | Duplicate Observed Data | Change Unidirectional Association to Bidirectional | Change Bidirectional Association to Unidirectional | Replace Magic Number with Symbolic Constant | Encapsulate Field | Encapsulate Collection | Replace Type Code with Class | Replace Type Code with Subclass | Replace Type Code with State/Strategy
Simplifying Conditional Expressions: Decompose Conditional | Consolidate Conditional Expression | Consolidate Duplicate Conditional Fragments | Remove Control Flag | Replace Nested Conditional with Guard Clauses | Replace Conditional with Polymorphism | Introduce Null Object | Introduce Assertion
Making Method Calls Simpler: Rename Method | Add Parameter | Remove Parameter | Separate Query from Modifier | Parameterise Method | Replace Parameter with Explicit Methods | Preserve Whole Object | Replace Parameter with Method | Introduce Parameter Object | Replace Parameter Object | Remove Setting Method | Hide Method | Replace Constructor with Factory Method | Encapsulate Downcast | Replace Error Code with Exception | Replace Exception with test
Dealing with Generalisation: Pull Up Field | Pull Up Method | Pull Up Constructor Body | Push Down Field | Push Down Method | Extract Subclass | Extract Superclass | Extract Interface | Collapse Hierarchy | Form Template Method | Replace Inheritance with Delegation
Big Refactorings: Tease Apart Inheritance | Convert Procedural Design to Objects | Separate Domain from Presentation | Extract Hierarchy

Retrieved from "https://oowisdom.csse.canterbury.ac.nz/index.php?title=Change_Unidirectional_Association_to_Bidirectional&oldid=9315"
Personal tools