Home >> All >> java >> beans >> [ beancontext Javadoc ]

• java.beans.beancontext: Javadoc index of package java.beans.beancontext.


Package Samples:

• java.beans.beancontext: Listeners and descriptors for managing beans.  

Classes:

• BeanContext: Acts as a container for sub-beans and as a sub-bean, so that an entire hierarchy of beans can be made up of BeanContext s. Since I can't sprinkle the Collections interface documentation with special information for BeanContext implementors, I'll have to document special requirements for implementors of those functions here. add() or addAll() : May add any Object into the hierarchy as well as a BeanContextChild , BeanContext or BeanContextProxy object. This way, any Bean can be in the hierarchy. Must synchronize on BeanContext.globalHierarchyLock . Don't add the Object if it's already there (only ...
• BeanContextChild: Beans implement this to get information about the execution environment and its services and to be placed in the hierarchy. The difference between a BeanContext and a BeanContextChild , mainly, is that a BeanContext may be a parent. BeanContextChild instances will be serialized at some point in their life, but you need to make sure your bean context does not contain a serializable reference (directly or indirectly) to the parent BeanContext , to any of the other BeanContext s in the tree, or to any resources obtained via the BeanContextServices interface. One way to do this is to mark any fields ...
• BeanContextProxy: Beans that wish to have a BeanContextChild or BeanContext associated with them but do not wish to implement those interfaces directly, can implement this interface. Don't shoot yourself in the foot: if you already implement BeanContextChild , directly or indirectly, the whole workings of this package will be unpredictable because it is indeterminate as to whether the BeanContextChild is used in preference to its proxy or vice versa.
• BeanContextServiceProvider: An actual factory for services. It is the BeanContextServiceProvider 's responsibility to register itself with whatever BeanContextServices object it wishes to provide services through using the addService() method. If for some reason it can no longer provide services for a particular class, this class must invoke BeanContextServices.revokeService(serviceClass,this,true) for all the places it has registered the service.
• BeanContextContainerProxy: Interface for BeanContext s which wish to associate an AWT container with them. The proxy is provided because the addPropertyChangeListener() and add() methods would conflict with Component and Container if you tried to extend.
• BeanContextServiceProviderBeanInfo: BeanContextServiceProvider s implement this to provide information about all of the services they provide. This is apparently so that you can import a bunch of services into a RAD tool and it will know about all of them and export them to the user in a readable manner.
• BeanContextChildComponentProxy: Interface for BeanContextChild s which wish to associate an AWT component with them. The proxy is provided because the addPropertyChangeListener() method would conflict with Component if you tried to extend.
• BeanContextMembershipEvent: Event fired when children are added to or removed from a BeanContext . Whether they were added or removed depends entirely on which method of the listener interface was called.
• BeanContextMembershipListener: This is the interface to which BeanContextMembershipEvent s are sent. This happens when children are added to or removed from a BeanContext .
• BeanContextChildSupport: Support for creating a BeanContextChild . This class contains the most common implementations of the methods in the BeanContextChild
• BeanContextServiceAvailableEvent: Event fired when new services become available through a BeanContextServices .
• BeanContextServiceRevokedEvent: Event fired when services are revoked from a BeanContextServices .
• BeanContextServices: Allows a BeanContext to provide services to its children.
• BeanContextEvent: Generic superclass for events fired by BeanContext s.
• BeanContextServicesListener: Listens for service add and revoke events.
• BeanContextServiceRevokedListener: Listens for service revoke events.
• BeanContextServicesSupport
• BeanContextSupport

Home | Contact Us | Privacy Policy | Terms of Service