Hello,
It appears that the empty keyword doesn't always
function on a collection. I must be missing something
obvious..
The folder object contains a collection of content.
The useBean tag isn't initializing the Folder object.
Its there so I can use scriptlet debugging code.
What exactly does
On Thu, 13 Feb 2003, Leon Doud wrote:
It appears that the empty keyword doesn't always
function on a collection. I must be missing something
obvious..
The folder object contains a collection of content.
The useBean tag isn't initializing the Folder object.
Its there so I can use
Wow. That is extremely unintuitive. Why not work on a Collection (which
automatically gives you List)?
-Original Message-
From: Shawn Bayern [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 11:13 AM
To: Tag Libraries Users List
Subject: Re: Problem with empty key word
It might be useful if we could see your JSP code, and any relevant bean code if it's
non-trivial.
-Original Message-
From: Schnitzer, Jeff [mailto:[EMAIL PROTECTED]]
Sent: Wed 02/12/2003 3:17 PM
To: [EMAIL PROTECTED]
Cc:
Well that would be fine if it was possible to call the
isEmpty() method on a collection. But since empty is
a key word the parser has a problem with
collection.empty.
Why not implement the empty keyword on all
collections? The method isEmpty is available in the
Collection interface. Was
On Thu, 13 Feb 2003, Leon Doud wrote:
Well that would be fine if it was possible to call the isEmpty()
method on a collection. But since empty is a key word the parser has
a problem with collection.empty.
You could use ${collection[empty]}.
Why not implement the empty keyword on all
Thanks! I forgot about that syntax.
--- Shawn Bayern [EMAIL PROTECTED] wrote:
On Thu, 13 Feb 2003, Leon Doud wrote:
Well that would be fine if it was possible to call
the isEmpty()
method on a collection. But since empty is a key
word the parser has
a problem with collection.empty.
From: Shawn Bayern [mailto:[EMAIL PROTECTED]]
Why not implement the empty keyword on all collections? The method
isEmpty is available in the Collection interface. Was there some
sort
of argument against that when the spec was defined?
I believe so; I don't remember the details of the
The problem occurs for a variety of JSP expressions, but the one from
the stack trace is: c:if test=${threadTool.player.moderator}
threadTool is a ThreadTool object in the request scope. It has an
inheritance chain like this:
ThreadTool extends ForumTool extends Paged extends AuthRequired
On Thu, 13 Feb 2003, Schnitzer, Jeff wrote:
From: Shawn Bayern [mailto:[EMAIL PROTECTED]]
Why not implement the empty keyword on all collections? The method
isEmpty is available in the Collection interface. Was there some
sort
of argument against that when the spec was defined?
I am running Tomcat 4.1.18 with JDK 1.4.1.01, and use the xtags directory
for server-side XSL transformation (XSLT). The first time I access the page
that includes XML to be displayed through xtags' XSLT, it works. The 2nd
time, it fails (see exception stack trace below), the 3rd time it works,
Hi,
I am considering using the DBtags in a project and I noticed that
version 1.0 beta 1 was released on August 21, 2001. Has this project
fallen by the wayside, or are people still working on it? If people
are still working on it, could they give a rough estimate of what
needs to be done for
Henri Yandell wrote:
On Thu, 13 Feb 2003, Schnitzer, Jeff wrote:
From: Shawn Bayern [mailto:[EMAIL PROTECTED]]
Why not implement the empty keyword on all collections? The method
isEmpty is available in the Collection interface. Was there some
sort
of argument against that when the
The difference is that Tomcat 4.1 comes with Jasper 2. Jasper 2 implements
JSP custom tag pooling. The XTags taglib most likely has some sort lifecycle
related bug that gets trigger when its tag handlers are pooled. You can
disable tag pooling in the JspServlet config in your
14 matches
Mail list logo
