java.beans.beancontext

Interface BeanContextChild

public interface 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 BeanContexts in the tree, or to any resources obtained via the BeanContextServices interface. One way to do this is to mark any fields that contain such references as transient. Another way is to use a custom serializer.

If you do not do this, when the BeanContext is serialized, all the other BeanContexts and other unnecessary things will be serialized along with it.

Before dying, a BeanContextChild should call getBeanContext().remove(this) to detach from the hierarchy and exit cleanly.

Since: JDK1.2

See Also: BeanContext

Method Summary
voidaddPropertyChangeListener(String prop, PropertyChangeListener listener)
Add a listener that will be notified when a specific property changes.
voidaddVetoableChangeListener(String prop, VetoableChangeListener listener)
Add a listener that will be notified when a specific property change is requested (a PropertyVetoException may be thrown) as well as after the change is successfully made.
BeanContextgetBeanContext()
Get the parent BeanContext.
voidremovePropertyChangeListener(String prop, PropertyChangeListener listener)
Remove a listener to a certain property.
voidremoveVetoableChangeListener(String prop, VetoableChangeListener listener)
Remove a listener to a certain property.
voidsetBeanContext(BeanContext parent)
Set the parent BeanContext.

Method Detail

addPropertyChangeListener

public void addPropertyChangeListener(String prop, PropertyChangeListener listener)
Add a listener that will be notified when a specific property changes.

Parameters: prop the name of the property to listen on listener the listener to listen on the property.

addVetoableChangeListener

public void addVetoableChangeListener(String prop, VetoableChangeListener listener)
Add a listener that will be notified when a specific property change is requested (a PropertyVetoException may be thrown) as well as after the change is successfully made.

Parameters: prop the name of the property to listen on listener the listener to listen on the property.

getBeanContext

public BeanContext getBeanContext()
Get the parent BeanContext.

Returns: the parent BeanContext.

removePropertyChangeListener

public void removePropertyChangeListener(String prop, PropertyChangeListener listener)
Remove a listener to a certain property.

Parameters: prop the name of the property being listened on listener the listener listening on the property.

removeVetoableChangeListener

public void removeVetoableChangeListener(String prop, VetoableChangeListener listener)
Remove a listener to a certain property.

Parameters: prop the name of the property being listened on listener the listener listening on the property.

setBeanContext

public void setBeanContext(BeanContext parent)
Set the parent BeanContext.

This method is called from BeanContext.add() and should not be called directly.

When this Object is being added to a new BeanContext or moved from an old one, a non-null value will be passed in.

When this Object is being removed from the current BeanContext, setBeanContext() will receive the parameter null.

When being removed from the current BeanContext, it is the BeanContextChild's responsibility to release all services it has obtained.

This change should generate PropertyChangeEvent and VetoableChangeEvents with the property name "beanContext". If the change is vetoed, it must re-throw the exception and not change anything. In this way, the parent BeanContextChild, who has registered himself with you, will have a chance to remove this child from its collection.

If the Bean does not wish to change the parent or be removed from one, it may throw the PropertyVetoException. If you veto a setBeanContext(null) call, then you should try your hardest to remedy whatever problem is keeping you from being removed from the BeanContext so that you can not veto it the next time. Otherwise, nasty pathological recursion stuff could occur in certain situations.

If you do veto the change, you must first back out any changes you made prior to the veto. Best not to make any such changes prior to the veto in the first place.

This method is called from BeanContext.add() and should not be called directly.

Parameters: parent the new parent for the BeanContextChild, or null to signify removal from a tree.

Throws: PropertyVetoException if the BeanContextChild implementor does not wish to have its parent changed.