| Used by control authors wishing to enforce rich semantic validation on extension and field
instance declarations of their controls. By supplying a ControlChecker implementation
(a "checker") and associating it with your control's public interface, when an
extension of your control is processed at build-time, the checker will be invoked and
can do rich validation of the extension type and field instances via introspection and
analysis of the control extension's type structure, signatures and annotations.
See Also: org.apache.beehive.controls.api.bean.ControlChecker |