|
.NET Framework | |||||||||
| PREV NAMESPACE NEXT NAMESPACE | FRAMES NO FRAMES | |||||||||
| Interface Summary | |
|---|---|
| IContext | Interface describing the application data context. This set of routines is used by the application to set and remove 'named' data object to pass them to the template engine to use when rendering a template. This is the same set of methods supported by the original Context class |
| InternalContextAdapter | interface to bring all necessary internal and user contexts together. this is what the AST expects to deal with. If anything new comes along, add it here. * I will rename soon :) * |
| InternalEventContext | Interface for event support. Note that this is a public internal interface, as it is something that will be accessed from outside of the .context package. |
| InternalHousekeepingContext | interface to encapsulate the 'stuff' for internal operation of velocity. We use the context as a thread-safe storage : we take advantage of the fact that it's a visitor of sorts to all nodes (that matter) of the AST during init() and render(). Currently, it carries the template name for namespace support, as well as node-local context data introspection caching. |
| InternalWrapperContext | interface for internal context wrapping functionality |
| Class Summary | |
|---|---|
| AbstractContext | |
| InternalContextAdapterImpl | |
| InternalContextBase | class to encapsulate the 'stuff' for internal operation of velocity. We use the context as a thread-safe storage : we take advantage of the fact that it's a visitor of sorts to all nodes (that matter) of the AST during init() and render(). Currently, it carries the template name for namespace support, as well as node-local context data introspection caching. * Note that this is not a public class. It is for package access only to keep application code from accessing the internals, as AbstractContext is derived from this. * |
| VMContext | This is a special, internal-use-only context implementation to be used for the new Velocimacro implementation. * The main distinguishing feature is the management of the VMProxyArg objects in the put() and get() methods. * Further, this context also supports the 'VM local context' mode, where any get() or put() of references that aren't args to the VM are considered local to the vm, protecting the global context. |
|
.NET Framework | |||||||||
| PREV NAMESPACE NEXT NAMESPACE | FRAMES NO FRAMES | |||||||||