|
Here are the observed behavior which is
important for anyone who is trying to work around this bug, and for anyone who
is trying to resolve this bug:
getServletConfig().getInitParameter(String name);
- Does not work ... always returns null.
getServletConfig().getServletContext().getInitParameter(String
name);
- Will work, but ONLY if you put your parameter in the
<context-param> </context-param> as shown below.
If the value is in the <init-param> </init-param>
tags (see below) it will NOT work.
Thank you,
Jason B.
-----Original Message----- From: Paul Hoepfner-Homme <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Thursday, October 26, 2000 1:00 PM Subject: Re: Frustration with getInitParameter Sorry, typo in web.xml below. I had <servlet-param>MyServlet</servlet-param> before, but it should be <servlet-class> obviously. I have fixed it below.Finally, I'm not alone!! I have 3.2 beta 6 as well. Here is a how I have web.xml set up: |
- Re: Frustration with getInitParameter William Brogden
- Re: Frustration with getInitPara... Paul Hoepfner-Homme
- RE: Frustration with getInitParameter Morahg, Yoav
- Re: Frustration with getInitParameter Paul Hoepfner-Homme
- Re: Frustration with getInitParameter Jason Bowman
- Re: Frustration with getInitParameter Paul Hoepfner-Homme
- Re: Frustration with getInitParameter Paul Hoepfner-Homme
- Re: Frustration with getInitParameter Craig R. McClanahan
- Re: Frustration with getInitParameter Bill Brooks
- Re: Frustration with getInitParameter Jason Bowman
- Jason Bowman
