Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OTExample Observer/Main"
(New page: ===Main program driving the Observer example=== <source lang="otj"> package flower_example; /** * @author Bruce Eckel (original Java example) * @author Miguel P. Monteiro (adaptation to...) |
|||
| Line 1: | Line 1: | ||
===Main program driving the Observer example=== | ===Main program driving the Observer example=== | ||
| − | <source lang="otj"> | + | <source lang="otj" line="1"> |
package flower_example; | package flower_example; | ||
/** | /** | ||
| Line 59: | Line 59: | ||
} | } | ||
</source> | </source> | ||
| + | |||
| + | This main program uses no special OT/J syntax, yet it applies some concepts specific to Object Teams: | ||
| + | |||
| + | ====Team activation==== | ||
| + | Lines 10-13 instantiate and activate the two pattern applications ({{otjld|5|}}). Similarly lines 52 and 53 clean up by deactivating both team instances. | ||
| + | |||
| + | ====Team methods==== | ||
| + | Lines 21ff, 36, 42 and 48 invoke team methods which have declared lifting {{otjld|2|.3.2}}. Note that to clients these methods look like regular Java methods, the '''as''' part of the signature is not part of the public API. | ||
| + | |||
| + | If you run this program you will notice how the reactions of the observers varies as they are register with and unregister from the pattern. Also a double ''open'' has no further effects. | ||
Latest revision as of 05:24, 24 February 2010
Main program driving the Observer example
package flower_example;
/*** @author Bruce Eckel (original Java example)* @author Miguel P. Monteiro (adaptation to OT/J)** Driver for this example of Observer*/public class Main {
public static void main(String[] args) {
ObservingOpen openingObs = new ObservingOpen();
ObservingClose closingObs = new ObservingClose();
openingObs.activate();
closingObs.activate();
Flower flower = new Flower();
Bee beeA = new Bee("A");
Bee beeB = new Bee("B");
Hummingbird birdA = new Hummingbird("A");
Hummingbird birdB = new Hummingbird("B");
openingObs.mapSubject2Observer(flower, birdA);
openingObs.mapSubject2Observer(flower, birdB);
openingObs.mapSubject2Observer(flower, beeA);
openingObs.mapSubject2Observer(flower, beeB);
closingObs.mapSubject2Observer(flower, birdA);
closingObs.mapSubject2Observer(flower, birdB);
closingObs.mapSubject2Observer(flower, beeA);
closingObs.mapSubject2Observer(flower, beeB);
System.out.println("Day 1: all observers follow the flower:");
flower.open();
flower.close();
System.out.println("Day 2: Hummingbird B decides to sleep in.");
openingObs.removeObserverFromSubject(flower, birdB);
flower.open();
System.out.println(" The flower is already open, no change:");
flower.open();
System.out.println("Bee A doesn't want to go to bed.");
closingObs.removeObserverFromSubject(flower, beeA);
flower.close();
System.out.println(" The flower is already closed, no change:");
flower.close();
System.out.println("Day 3: All observers lose interest in the flower's opening.");
openingObs.removeAllObserversFromSubject(flower);
flower.open();
flower.close();
openingObs.deactivate();
closingObs.deactivate();
System.out.println("\nterminated.");
}}
This main program uses no special OT/J syntax, yet it applies some concepts specific to Object Teams:
Team activation
Lines 10-13 instantiate and activate the two pattern applications (OTJLD §5). Similarly lines 52 and 53 clean up by deactivating both team instances.
Team methods
Lines 21ff, 36, 42 and 48 invoke team methods which have declared lifting OTJLD §2.3.2. Note that to clients these methods look like regular Java methods, the as part of the signature is not part of the public API.
If you run this program you will notice how the reactions of the observers varies as they are register with and unregister from the pattern. Also a double open has no further effects.