Hello Chris and Konstantin,
thanks for all your suggestions - we finally tracked down the issue,
and it turns out the root cause here was a flawed deployment process.
In order to preserve the application's context.xml file during
software upgrades, our service engineers stop Tomcat, then remove
2010/8/12 Thomas Treitlinger ttreitlin...@gmail.com:
Hello,
I have a number of JSP pages which use the JSTL core library to set a
request attribute like this:
c:set var=foo scope=request FOO-VALUE/c:set
The JSPs then forward to a Servlet like this:
jsp:forward page=/request.go /
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas,
On 8/13/2010 8:23 AM, Thomas Treitlinger wrote:
%@ taglib prefix=c uri=http://java.sun.com/jsp/jstl/core; %
Something just occurred to me: do you have a servlet 2.5 version
declared in your webapp's web.xml file? If not, I think you'll want
Hi Chris,
thanks for your reply. Using your code, I get the same output, and
unable to print the value using c:out, but that's not what I'm
trying to do.
Most of the time this application works as intended, here is some more detail:
* The JSPs are dumb landing pages - only used to track which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas,
On 8/13/2010 8:23 AM, Thomas Treitlinger wrote:
Using your code, I get the same output, and
unable to print the value using c:out, but that's not what I'm
trying to do.
Right: I was just wondering if there was some other misconfiguration
Hello,
I have a number of JSP pages which use the JSTL core library to set a
request attribute like this:
c:set var=foo scope=request FOO-VALUE/c:set
The JSPs then forward to a Servlet like this:
jsp:forward page=/request.go /
The Servlet later invokes
String s = (String)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/12/2010 9:25 AM, Thomas Treitlinger wrote:
Hello,
I have a number of JSP pages which use the JSTL core library to set a
request attribute like this:
c:set var=foo scope=request FOO-VALUE/c:set
The JSPs then forward to a Servlet like
