Home >> All >> org >> apache >> velocity >> [ context Javadoc ]

• org.apache.velocity.context: Javadoc index of package org.apache.velocity.context.


Package Samples:

• org.apache.velocity.context

Classes:

• InternalContextAdapterImpl: This adapter class is the container for all context types for internal use. The AST now uses this class rather than the app-level Context interface to allow flexibility in the future. Currently, we have two context interfaces which must be supported : Context : used for application/template data access InternalHousekeepingContext : used for internal housekeeping and caching InternalWrapperContext : used for getting root cache context and other such. InternalEventContext : for event handling. This class implements the two interfaces to ensure that all methods are supported. When adding to the interfaces, ...
• AbstractContext: This class is the abstract base class for all conventional Velocity Context implementations. Simply extend this class and implement the abstract routines that access your preferred storage method. Takes care of context chaining. Also handles / enforces policy on null keys and values : Null keys and values are accepted and basically dropped. If you place an object into the context with a null key, it will be ignored and logged. If you try to place a null into the context with any key, it will be dropped and logged. The default implementation of this for application use is org.apache.velocity.VelocityContext. ...
• 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.
• 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.
• Context: 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.
• InternalWrapperContext: interface for internal context wrapping functionality

Home | Contact Us | Privacy Policy | Terms of Service