Hi there!
I am using dbtags lib for accessing database from client side (jsp). It
works fine with Tomcat3.0, but when I use the same thing in Tomcat4.0 it's
falling over.
The error reads -
java.lang.VerifyError: (class: org/apache/jsp/log$jsp, method: _jspService
signature:
I have some code that runs something like this:
c:set value=${pageContext.request.queryString} var=section/
c:if test=${empty section}
c:set value=home var=section/
/c:if
c:set value=/scripts/headlines.jsp?section=${section} var=headlines/
jsp:include page=${headlines} flush=true/
I am
On Mon, 12 Aug 2002, Ben Ramsey wrote:
jsp:include page=${headlines} flush=true/
[...]
Am I doing something wrong?
In JSP 1.2, you can't use the JSTL expression language in JSP standard
actions like jsp:include. JSTL can't change the JSP standard on its
own, and so JSTL expressions are
In the meantime, you'll need either to use c:import
as a substitute for jsp:include or use an rtexprvalue
with jsp:include.
Can c:import include pages dynamically, or must the pages be static. For
example, I'm passing this querystring to the page so that the page can
process it and deliver
On Mon, 2002-08-12 at 10:02, Ben Ramsey wrote:
In addition, I've placed th variable into the page attribute using the scripting
tags: %= headlines %,
but I get a variable undefined error for headlines.
In addition to what Shawn said, if you want to use an RT value with
jsp:include, you will
On Mon, 12 Aug 2002, Ben Ramsey wrote:
In the meantime, you'll need either to use c:import
as a substitute for jsp:include or use an rtexprvalue
with jsp:include.
Can c:import include pages dynamically, or must the pages be static.
For example, I'm passing this querystring to the
However, you should use nested c:param tags to pass
query parameters. E.g.,
c:import url=foo.jsp
c:param name=user value=${user} /
/c:import
Thanks, works like a charm!
Ben Ramsey
Technical Director
EUREKA! Interactive, Inc.
770-642-0390
www.eureka-interactive.com
--
To
Madhavi wrote:
I am using dbtags lib for accessing database from client side (jsp).
It works fine with Tomcat3.0, but when I use the same thing in Tomcat4.0
it's
falling over.
The error reads -
java.lang.VerifyError: (class: org/apache/jsp/log$jsp, method: _jspService
signature:
I started seeing this same error yesterday while working on a taglib based
on DBTags. I'm using Tomcat 3.3.1. All I did was change my tag from
BodyTagSupport to TagSupport, and deleted the doStartTag and doAfterEndTag
(?) methods. It still compiled with no errors, but gave the 'Incompatible
It looks like not using the class U have mentioned causes the problem -
Incompatible object argument for function call
Nothing that refers to BodyTagSupport class or doStartTag,
doAfterEndTag methods.
Am I missing something here?? (sorry, if I am asking a funny question -
Obviously I am
Thanks for the tip!
-Madhavi
I'm actually making changes to the source code, so I'm working with those
methods I mentioned. The error messages don't refer to those methods, but I
found that when I removed them and changed my tag (which is based on one of
the DBTags classes) from extending
basicportal.sourceforge.net uses JSTL with JDBC among other things.
The Kelley's wrote:
Can anyone show me how to use JNDI for a JDBC database using JSTL in Tomcat
4.03? I need a simple example.
Tim
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
12 matches
Mail list logo
