## Uses of Interface
org.apache.velocity.tools.view.JeeConfig

### Uses of JeeConfig in org.apache.velocity.tools.view

Classes in org.apache.velocity.tools.view that implement JeeConfig
`class` `JeeContextConfig` Implements `JeeConfig` with only a `ServletContext`.
`class` `JeeFilterConfig` Implements `JeeConfig` with a `FilterConfig`.
`class` `JeeServletConfig` Implements `JeeConfig` with a `ServletConfig`.

Methods in org.apache.velocity.tools.view with parameters of type JeeConfig

`protected void`

VelocityView.`configure(JeeConfig config, ToolboxFactory factory)`
Here's the configuration lookup/loading order: If loadDefaults is true, `ConfigurationUtils.getDefaultTools()` Config file optionally specified by servletContext `org.apache.velocity.tools` init-param Config file optionally at `/WEB-INF/tools.xml` (conventional location) Config file optionally specified by servlet `org.apache.velocity.tools` init-param Remember that as these configurations are added on top of each other, the newer values will always override the older ones.

`protected void` VelocityView.`configure(JeeConfig config, org.apache.velocity.app.VelocityEngine velocity)`
`static VelocityView` ServletUtils.`getVelocityView(JeeConfig config)` Returns the shared `VelocityView` for the specified `JeeConfig`'s context.
`protected void` VelocityView.`init(JeeConfig config)` Initializes ToolboxFactory, VelocityEngine, and sets default encoding for processing requests.
`protected void` VelocityView.`init(JeeConfig config, org.apache.velocity.app.VelocityEngine velocity)` Initializes the Velocity runtime, first calling loadConfiguration(JeeConfig) to get a java.util.Properties of configuration information and then calling velocityEngine.init().
`protected void` VelocityView.`setEncoding(JeeConfig config)`

Constructors in org.apache.velocity.tools.view with parameters of type JeeConfig
Constructor and Description
`VelocityView(JeeConfig config)`