Table of Contents
Previous Section
If you have an applet, but do not have the source code for it, you must follow the following strategy for making the applet a client-side component. You must know the applet's accessor methods for setting and getting state, and, if the applet triggers actions, there must be some way for your Association to detect this. If the applet doesn't have API for getting and setting state, you cannot make the applet into a client-side component.
class MyAssociation extends Association { // ... }
synchronized public Object valueForKey(String key) { Object dest = this.destination(); if (key.equals("title")) { return ((MyApplet)dest).getLabel(); } } synchronized public void takeValueForKey(Object value, String key) { Object dest = this.destination(); if (key.equals("title")) { if ((value != null) && !(value instanceof String)) { System.out.println("Object value of wrong type set for key 'title'. Value must be a String."); } else { ((MyApplet)dest).setLabel(((value == null) ? "" : (String)value)); } }
Note that the class of the destination applet ("MyApplet" in the example) must be cast.
If the applet triggers an action method, it must some mechanism for communicating this event to observers (such as an "observeGadget()" method).
public void observeGadget(Object sender, String action) { // fictictious if ((sender instanceof Gadget) && action.equals("vacuum")) { this.invokeAction(action); } }Note that in this hypothetical example, the Association must first set itself up as an observer.