Howdy,
Your context constructor? What's that? Last I checked,
javax.servlet.ServletContext was an interface, and the container
provides an implementation.
If you want to tie into the context lifecycle, which is a very valid
design, use a ServletContextListener implementation. The context
Sorry 2 different Contexts, and my brain was all messed up. When I'm refering to my Context
Constructor it's actually the main servlet constructor (which in our app is PolarisContext). Which
extends HttpServlet.
Sorry for the confusion
Shapira, Yoav wrote:
Howdy,
Your context constructor?
Howdy,
Sorry 2 different Contexts, and my brain was all messed up. When I'm
refering to my Context
Constructor it's actually the main servlet constructor (which in our
app is
PolarisContext). Which
extends HttpServlet.
OK, that makes a bit more sense. Although a similar argument applies.
Even
Shapira, Yoav wrote:
Howdy,
Sorry 2 different Contexts, and my brain was all messed up. When I'm
refering to my Context
Constructor it's actually the main servlet constructor (which in our
app is
PolarisContext). Which
extends HttpServlet.
OK, that makes a bit more sense. Although a
Howdy,
Ok that worked great. I don't get the exceptions anymore but for some
reason it's not pulling the
params from the web.xml. Any Ideas?
If the code below is taken from a servlet, then this.getInitParameter()
will look for an init-parameter element inside the servlet element.
To get a
Shapira, Yoav wrote:
Howdy,
Ok that worked great. I don't get the exceptions anymore but for some
reason it's not pulling the
params from the web.xml. Any Ideas?
If the code below is taken from a servlet, then this.getInitParameter()
will look for an init-parameter element inside the
