Steve-- Right -- the doc is correct, a subclass of the o.a.b.c.r.b.ControlBean class is code generated at build time by the Controls annotation processor. This class contains lots of additional operations that can be performed on a Control which can affect the implementation.
For example, given a Foo control interface (and impl), the annotation processor generates a FooBean. This ControlBean subclass has a set of methods to support: - configuring a Control's annotation properties through JavaBean getters and setters - registering event handlers for control and resource context events - getting the metadata configured for various parts of a Control and so on. A Control client would access the FooBean anytime that a developer needs to / wants to configure these manually. To see these generated ControlBean subclasses, you can just look at the code generated when building the controls-blank/ sample in the Beehive distribution. And, take a look at the ControlBean base class in the trunk/controls/src/runtime source directory. Hope that helps! Eddie On 1/13/06, Steve Hanson <[EMAIL PROTECTED]> wrote: > Hi all: > > The controls overview doc mentions the "Control Bean Wrapper" as one of the > keystones in control architecture ( > http://localhost:8888/controls/overview.html#Public+Interface+%2F+Private+Implementation+%2F+ControlBean+Wrapper > ). > > Just a quick question about this: is there ever a case where the user would > author this class directly? Or is this always a build artifact? > > thanks, > steveh. > >
