Scope implementation.Note
This thread scope is not registered by default in common contexts.
Instead, you need to explicitly assign it to a scope key in your setup, either through
org.
or through a org. bean.
SimpleThreadScope does not clean up any objects associated with it.
It is therefore typically preferable to use a request-bound scope implementation such
as org.springframework.web.context.request.RequestScope in web environments,
implementing the full lifecycle for scoped attributes (including reliable destruction).
For an implementation of a thread-based Scope with support for destruction
callbacks, refer to
Spring by Example.
Thanks to Eugene Kuleshov for submitting the original prototype for a thread scope!
org.springframework.web.context.request.RequestScope
| Modifier and Type | Field and Description |
|---|---|
| private static final Log | |
| private final ThreadLocal |
| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| public Object | get(String
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 mechanismImplements org. Return the object with the given name from the underlying scope,
|
| public String | getConversationId()
Implements org. Return 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)Implements org. 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 | remove(String
the name of the object to remove name)Implements org. Remove the object with the given |
| public Object | resolveContextualObject(String
the contextual key key)Implements org. Resolve the contextual object for the given key, if any. |
| logger | back to summary |
|---|---|
| private static final Log logger | |
| threadScope | back to summary |
|---|---|
| private final ThreadLocal<Map<String, Object>> threadScope | |
| SimpleThreadScope | back to summary |
|---|---|
| public SimpleThreadScope() | |
| get | back to summary |
|---|---|
| public Object get(String name, ObjectFactory<?> objectFactory) Implements org. Doc from org. 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() Implements org. Doc from org. 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) Implements org. Doc from org. 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) Implements org. Doc from org. 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) Implements org. Doc from org. Resolve the contextual object for the given key, if any. E.g. the HttpServletRequest object for key "request". | |