OK, so I tried that and found one library needs to be excluded (from the
exclusion list) - i.e. scanned
# ls jstl*; grep ".tld" jstl-*
jstl-api-1.2.jar jstl-impl-1.2.jar
Binary file jstl-impl-1.2.jar matches
So if your rule works, I need jstl-impl to be scanned, but jstl-api could be
excluded.
On Mon, Nov 06, 2017 at 10:13:42AM -0500, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Ray,
>
> On 11/6/17 9:48 AM, Ray Holme wrote:
> > I am not the primary developer. I do Java and DB development. I
> > leave the JSP for someone else (I am mostly retired bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ray,
On 11/6/17 9:48 AM, Ray Holme wrote:
> I am not the primary developer. I do Java and DB development. I
> leave the JSP for someone else (I am mostly retired but I have
> been doing this a LONG time).> But I deal with distributions and
> builds
Chris,
I am not the primary developer. I do Java and DB development.
I leave the JSP for someone else (I am mostly retired but I have been doing
this a LONG time).
But I deal with distributions and builds so I was the one who modified the "not
to SCAN" libraries.2.5 minutes down to less than 1 se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ray,
On 11/6/17 8:49 AM, Ray Holme wrote:
> So according to Mark, taglibs must NOT be listed in the
> catalina.properties file under
> tomcat.util.scan.StandardJarScanFilter.jarsToSkip Mark informed us
> that the below jstl... jars are both taglibs:
On 8/8/06, Le Nguyen-Thinh <[EMAIL PROTECTED]> wrote:
My JSP contains a piece of code which calls a tag from the taglib above:
What in the world is that supposed to be referring to?
java.lang.NumberFormatException: For input string: "${0}"
Try:
(assuming MAX is actually set somewhere
Thanks all for your advice.
My web.xml has an entry:
!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd";>
which, I think, caused the error.
I have inserted the line:
<%@ page ... isELIgnored="false" %>
as Pid sugges
One other possibility -- which servlet spec version do you have
specified in your web.xml? If web.xml declares an older version of the
servlet spec, these ${} expressions may not be available.
--David
Pid wrote:
which version of tomcat are you using?
is Expression Language enabled? as it l
which version of tomcat are you using?
is Expression Language enabled? as it looks like it's passing the ${0}
variable as a string rather than evaluating it.
Try setting the following attribute in your JSP 'page' directive.
<%@ page ... isELIgnored="false" %>
Le Nguyen-Thinh wrote:
> Dear frie
