I'm glad your just as confused as I am, since I honestly don't know
either :)
I was hoping you'd have the magic answer, but looks like I'll have to
dig around this weekend to figure what the exact cause is. thanks for
responding to my obtuse questions, since I'm confused as to why this
behavior
On Fri, 18 Oct 2002, peter lin wrote:
> it's only when the syntax is incorrect that it doesn't throw an
> exception like "symbol cannot be resolved", "clascastexception" or
> some other exception. Right or wrong, I expect the EL to realize
> "duh, that's the wrong syntax silly pete. I'm throwing
without EL it works fine. I've tried with scriplet code and it works
fine. I've tried it with the correct syntax and it works fine.
it's only when the syntax is incorrect that it doesn't throw an
exception like "symbol cannot be resolved", "clascastexception" or some
other exception. Right or w
On Fri, 18 Oct 2002, peter lin wrote:
> It causes tomcat 4.1.12 to generate logs continuously. If I don't hit
> stop in the browser, it will continue to generate logs. After a couple
> of minutes, the log is tens of megs.
>
> I don't know if it's the responsibility of the EL to throw an
> excepti
It causes tomcat 4.1.12 to generate logs continuously. If I don't hit
stop in the browser, it will continue to generate logs. After a couple
of minutes, the log is tens of megs.
I don't know if it's the responsibility of the EL to throw an exception
or if jasper should be responsible. with is why
On Thu, 17 Oct 2002, peter lin wrote:
> It looks like using won't retrieve
> the value, since acookie is a hashentry, it can't do
> acookie.getName().toString(). I'm guessing that is correct
> functionality right?
Right, for ${cookie} is a Map of all cookie names to Cookie instances.
So, in th
I wrote a basic test page and this is the result I get.
output
print out the classname
java.util.HashMap$Entry
java.util.HashMap$Entry
java.util.HashMap$Entry
print out the cookie
id1=value_for_id1
JSESSIONID=1B6A8CE1F51A31E335719420A239BEB2
id2
we did verify "acookie" exists. I should have been more clear in my
original email.
shouldn't JSTL throw an exception, since "acookie" is wrapped, so using
is the correct syntax. Using
should throw an exception, rather than
go into an infinite loop and generate megs of error logs?
peter
S
I will dig deeper and post my findings.
thanks
peter
Shawn Bayern wrote:
>
> On Thu, 17 Oct 2002, peter lin wrote:
>
> > we did verify "acookie" exists. I should have been more clear in my
> > original email.
>
> That's not really the issue; the question is what's causing the error
> logs th
On Thu, 17 Oct 2002, peter lin wrote:
> we did verify "acookie" exists. I should have been more clear in my
> original email.
That's not really the issue; the question is what's causing the error
logs that you're suggesting are indicative of a bug. Since the Standard
Taglib simply results 'acook
On Thu, 17 Oct 2002, peter lin wrote:
> But if I use this syntax, it causes tomcat to generate a ton of logs.
>
>
To determine whether this is a bug in JSTL or in Tomcat, try replacing
this tag with a scriptlet that performs the equivalent operation --
something like
<%= ((Cookie) pageContex
A co-worker discovered strange behavior, which may be a bug. We're
trying to print out cookie values to the page for testing and noticed it
generates several megs of application errors.
if we use the following syntax with a forEach, to access cookie, it
works.
But if I use this syntax, it caus
12 matches
Mail list logo
