ConfigurableBeanFactory,
representing a target scope to hold bean instances in.
This allows for extending the BeanFactory's standard scopes
"singleton" and
"prototype"
with custom further scopes, registered for a
specific key.
org. implementations
such as a org.
may register additional standard scopes specific to their environment,
e.g. "request"
and "session",
based on this Scope SPI.
Even if its primary use is for extended scopes in a web environment,
this SPI is completely generic: It provides the ability to get and put
objects from any underlying storage mechanism, such as an HTTP session
or a custom conversation mechanism. The name passed into this class's
get and remove methods will identify the
target object in the current scope.
Scope implementations are expected to be thread-safe.
One Scope instance can be used with multiple bean factories
at the same time, if desired (unless it explicitly wants to be aware of
the containing BeanFactory), with any number of threads accessing
the Scope concurrently from any number of factories.
ConfigurableBeanFactory#registerScope, CustomScopeConfigurer, org.springframework.aop.scope.ScopedProxyFactoryBean , org.springframework.web.context.request.RequestScope , org.springframework.web.context.request.SessionScope
| Modifier and Type | Method and Description |
|---|---|
| public Object | Returns: the desired object (nevernull)the name of the object to retrieve name, ObjectFactory<?> the objectFactory)ObjectFactory to use to create the scoped
object if it is not present in the underlying storage mechanismReturn the object with the given name from the underlying scope,
|
| public String | Returns: the conversation ID, ornull if there is no
conversation ID for the current scopeReturn the conversation ID for the current underlying scope, if any. |
| public void | registerDestructionCallback(String
the name of the object to execute the destruction callback for name, Runnable 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. callback)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). |
| public Object | |
| public Object | Returns: the corresponding object, ornull if none foundthe contextual key key)Resolve the contextual object for the given key, if any. |
| get | back to summary |
|---|---|
| public Object get(String name, ObjectFactory<?> objectFactory) Return the object with the given name from the underlying scope,
This is the central operation of a Scope, and the only operation that is absolutely required.
| |
| getConversationId | back to summary |
|---|---|
| public String getConversationId() Return the conversation ID for the current underlying scope, if any. The exact meaning of the conversation ID depends on the underlying
storage mechanism. In the case of session-scoped objects, the
conversation ID would typically be equal to (or derived from) the
Note: This is an optional operation. It is perfectly valid to
return
| |
| registerDestructionCallback | back to summary |
|---|---|
| public void registerDestructionCallback(String name, Runnable callback) 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). 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 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
| |
| remove | back to summary |
|---|---|
| public Object remove(String name) Remove the object with the given Returns 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
| |
| resolveContextualObject | back to summary |
|---|---|
| public Object resolveContextualObject(String key) Resolve the contextual object for the given key, if any. E.g. the HttpServletRequest object for key "request".
| |