|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
The Pull Service manages the creation of application tools that are available to all templates in a Turbine application. By using the Pull Service you can avoid having to make Screens to populate a context for use in a particular template. The Pull Service creates a set of tools, as specified in the TR. props file.
These tools can have global scope, request scope, session scope (i.e. stored in user temp hashmap) or persistent scope (i.e. stored in user perm hashmap).
The standard way of referencing these global tools is through the toolbox handle. This handle is typically $toolbox, but can be specified in the TR. props file.
So, for example, if you had a UI Manager tool which created a set of UI attributes from a properties file, and one of the properties was 'bgcolor', then you could access this UI attribute with $ui.bgcolor. The identifier that is given to the tool, in this case 'ui', can be specified as well.
Field Summary | |
static java.lang.String |
ROLE
The Avalon role |
Method Summary | |
void |
populateContext(ViewContext context,
RunData data)
Populate the given context with all request, session and persistent scope tools (it is assumed that the context already wraps the global context, and thus already contains the global tools). |
void |
releaseTools(ViewContext context)
Release tool instances from the given context to the object pool |
Field Detail |
public static final java.lang.String ROLE
Method Detail |
public void populateContext(ViewContext context, RunData data)
context
- a ViewContext to populatedata
- a RunData object for request specific datapublic void releaseTools(ViewContext context)
context
- a ViewContext to release tools from
|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |