Hi,
I am used to accessing form and URL parameters from JSTL using
${param.something}.
However, I've found if a form is enctype=multipart/form-data then the
parameters defined within the form tags are not accessible.
Say if I had a form field that was type=text (or hidden) then the value is
-Original Message-
From: Andrew Stevens [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 18, 2004 11:13 PM
To: '[EMAIL PROTECTED]'
Subject: ${param.something} ... feature or bug?
Hi,
I am used to accessing form and URL parameters from JSTL using
${param.something}.
However,
Hi,
this is exactly the error that I receive whit the xtags library used on
tomcat 5.016
The same code worked correctly with tomcat 4.xx, and work correctly
still now but just for 5-10 times,
after this period I receive the error and I have to recompile the jsp again.
Is it possible that this
Hi,
Please help.
What I would like to do is redirect, or forward, to another page when an
exception occurs in certain JSP pages.
I call some JSPs that utilize beans (via JSTL) that have getter methods
which perform database access. These getter methods can generate exceptions.
When they do, the
What we do is catch the exception in the Java code and redirect from the Java code,
not the JSP itself.
Karl
-Original Message-
From: Frank Burns [mailto:[EMAIL PROTECTED]
Sent: Monday, April 19, 2004 9:03 AM
To: Tag Libraries Users List
Subject: Help with handling exceptions
Hi,
Hi,
I suspect this has been asked numerous times before, but I could not
find a FAQ for JSTL: I set up jstl for my web-app(on tomcat 5) by:
- copying the tld's to web-inf
- adding the taglibs to web.xml
- announcing the used taglibs on the jsp
The tags get correctly evaluated (I suppose...) but
okok,
maybe just look into the code before posting:
the web-app-tag of the web.xml did not point to the 2.4-version, adding
web-app xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
Hi -
We are using the JSTL 1.0.4. We have noticed that the ELEvaluator caches all results
from coercing a literal to an Object. This is causing incorrect results and a memory
leak for our application.
Here are our details. We have an object of type MyObject with a name property. This
name
