Pattern parameter dependencies are created between only two parameters. The Pattern Authoring view allows the entry of multiple supplier or client parameters per parameter, but this in turn generates multiple parameter dependencies for each pair of the indicated parameters. For example, if the parameter being edited is named "A", and "X" and "Y" are the supplier parameters then two parameter dependencies are attached to the parameter "A". Each parameter dependency's purpose is to receive notice when the supplier parameter of interest is modified. One parameter dependency located in "A" is updated when "X" changes, and the other one that is also located in "A", is updated when "Y" changes.
When parameter dependencies are added, the framework inserts update methods known as hot spots into the class for the designated client parameter. The pattern author adds Java code to the update method to provide the behaviors for partial or delayed expansion based on the needs of the design.
A pattern author defines a parameter dependency when the state change of a given parameter's arguments is of interest to another parameter's arguments. For example, when one parameter gets a new argument bound, another parameter argument might need to update its state to take this new binding into account.
To add or edit parameter dependencies by using the Pattern Authoring view: