public interface JeeConfig
Because sometimes you don't care about the difference between a
servlet and a filter. Why isn't there a common interface for
FilterConfig and ServletConfig already? Sheesh.
Anyway, this also adds the ability to fake everything if you don't have
either a FilterConfig or a ServletConfig handy. Just implement it and
override the methods that return things you care about. Oh, and if you don't
have any init-params at all, just use JeeContextConfig as
ServletContext is the only really essential thing for creating a
VelocityView.
| Modifier and Type | Method and Description |
|---|---|
java.lang.String |
findInitParameter(java.lang.String key)
Looks for the specified init-param in the servlet/filter config
(i.e.
|
java.lang.String |
getInitParameter(java.lang.String name)
Returns an initialization parameter.
|
java.util.Enumeration |
getInitParameterNames()
Returns all the parameter names.
|
java.lang.String |
getName()
Returns the name of the servlet (or filter) being used.
|
ServletContext |
getServletContext()
Returns the servlet context.
|
java.lang.String getInitParameter(java.lang.String name)
name - The name of the initialization parameter.java.lang.String findInitParameter(java.lang.String key)
getInitParameter(java.lang.String)). If no such init-param is
found there, it checks the ServletContext's init-params
for the specified parameter.key - The name of the initialization parameter.java.util.Enumeration getInitParameterNames()
java.lang.String getName()
ServletContext getServletContext()
Copyright (c) 2003-2007 Apache Software Foundation