public class DestructionAwareAttributeHolder extends java.lang.Object implements java.io.Serializable
|Constructor and Description|
|Modifier and Type||Method and Description|
Clears the map by removing all registered attribute values and invokes every destruction callback registered.
Returns the attribute having the specified name, if available,
Returns the map representation of the registered attributes directly.
Returns the destruction callback, if any registered for the attribute with the given name or
Register a callback to be executed on destruction of the specified object in the scope (or at destruction of the entire scope, if the scope does not destroy individual objects but rather only terminates in its entirety).
Remove the object with the given
Puts the given object with the specified name as an attribute to the underlying map.
public java.util.Map<java.lang.String,java.lang.Object> getAttributeMap()
public java.lang.Object getAttribute(java.lang.String name)
name- the name of the attribute to be returned
nullif not available
public java.lang.Object setAttribute(java.lang.String name, java.lang.Object value)
name- the name of the attribute
value- the value to be stored
public java.lang.Object removeAttribute(java.lang.String name)
namefrom the underlying scope.
null if no object was found; otherwise returns the
Note that an implementation should also remove a registered destruction callback for the specified object, if any. It does, however, not need to execute a registered destruction callback in this case, since the object will be destroyed by the caller (if appropriate).
Note: This is an optional operation. Implementations may throw
UnsupportedOperationException if they do not support explicitly
removing an object.
name- the name of the object to remove
nullif no object was present
public void clear()
public void registerDestructionCallback(java.lang.String name, java.lang.Runnable callback)
Note: This is an optional operation. This method will only be called for scoped beans with actual destruction configuration (DisposableBean, destroy-method, DestructionAwareBeanPostProcessor). Implementations should do their best to execute a given callback at the appropriate time. If such a callback is not supported by the underlying runtime environment at all, the callback must be ignored and a corresponding warning should be logged.
Note that 'destruction' refers to to automatic destruction of the object
as part of the scope's own lifecycle, not to the individual scoped object
having been explicitly removed by the application. If a scoped object
gets removed via this facade's
any registered destruction callback should be removed as well, assuming
that the removed object will be reused or manually destroyed.
name- the name of the object to execute the destruction callback for
callback- the destruction callback to be executed. Note that the passed-in Runnable will never throw an exception, so it can safely be executed without an enclosing try-catch block. Furthermore, the Runnable will usually be serializable, provided that its target object is serializable as well.
public java.lang.Runnable getDestructionCallback(java.lang.String name, boolean remove)
nullif no such callback was registered.
name- the name of the registered callback requested
true, if the callback should be removed after this call,
false, if it stays