Hi,
I am evaluating the migration to Tomcat from Resin and encounted the
following problem.
The following exception is raised when I am trying to use tag libraries
packaged as JAR files in the web application with both Tomcat 5.5.9 or
5.5.11 (I have the JAR file with the tld in META-INF/tlds
Hi,
The following line:
c:set var=admin value=%=request.getParameter(admin)%/
gives me the below exception under Tomcat 5.5.9:
org.apache.jasper.JasperException: /test.jsp(11,29) The value of
attribute value associated with an element type c:set must not
contain the '' character.
Is
Message-
From: Rahul Akolkar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 2:10 PM
To: Tomcat Users List
Subject: Re: org.apache.jasper.JasperException using jsp expression
inside the c:set /
On 8/24/05, Seva Popov [EMAIL PROTECTED] wrote:
Hi,
The following line
I would appreciated the pointers to the specs.
--Seva
-Original Message-
From: Rahul Akolkar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 4:23 PM
To: Tomcat Users List
Subject: Re: org.apache.jasper.JasperException using jsp expression
inside the c:set /
On 8/24/05, Seva
Hi,
I have the JAR file with the custom tag library in META-INF/tlds
directory.
My test.jsp page:
jsp:root xmlns:jsp=http://java.sun.com/JSP/Page;
xmlns:ui=http://www.metatv.com/common/ui/tags-test;
version=2.0
test:print/
/jsp:root
The following exception is raised when I
Hi,
I believe the name of the JAASRealm's useContextClassLoader flag (and
the relevant Tomcat 5.5.* documentation) is misleading. Let's look at
the source code:
org.apache.catalina.realm.JAASRealm:
...
// What if the LoginModule is in the container class loader ?
ClassLoader
Woodchuck,
I guess, the alternative solution is to have all your web apps use log4j
as well.
So, you have commons-logging.jar and log4j.jar in the
${Tomcat}/common/lib folder
and log4j.properties in ${Tomcat}/common/classes folder.
Just add into your each web app's WEB-INF/classes folder
-
From: Woodchuck [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 06, 2005 11:10 AM
To: Tomcat Users List; Seva Popov
Subject: RE: Tomcat 5.5 classloader log4j vs JCL issue
hihi Seva,
yes, your suggestion also works. i tried it to confirm, and it was my
backup plan to do in case i couldn't
Hi,
I need to use the JSP 2.0 runtime expressions in the attribute values of
JSTL 1.1 tags but I am getting the exception when I try to use them.
My jsp page:
jsp:root xmlns:jsp=http://java.sun.com/JSP/Page;
xmlns:c=http://java.sun.com/jsp/jstl/core;
runtime expressions in the attribute values
of JSTL 1.1
For example Resin does allow it.
Any ideas?
-Original Message-
From: Seva Popov [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 13, 2005 12:59 PM
To: Tomcat Users List
Subject: Tomcat 5.5.9 and JSP 2.0 runtime expressions
PM
To: Tomcat Users List
Subject: Re: Tomcat 5.5.9 and JSP 2.0 runtime expressions in the attribute
values of JSTL 1.1
On 9/13/05, Seva Popov [EMAIL PROTECTED] wrote:
BTW, I understand that I can use a different syntax with the runtime
expressions. So, if I change my jsp (not use the xml
The type in Java is a combination of a fully qualified class name and its
defining classloader. So the two objects with the same class name are
considered different types in your two web applications because each web
application is loaded by the dedicated webapp classloader.
To solve your
Yes, using the shared classloader seems like an obvious and easy option for
sharing the objects between the web applications. However, like the previous
author notes relying on the classloader can bring up some issues like
introducing new dependencies and reducing the web application
13 matches
Mail list logo
