On Thursday, February 13, 2003, at 05:04 PM, Pierre Delisle wrote:
The change that Jeff is proposing, although of interest, would
unfortunately break compatibility with the spec.
(sorry guys, but the Expert Group ain't perfect)
Why would extending the empty keyword to support Collections
-Original Message-
From: James Cook [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 14, 2003 8:17 AM
To: Tag Libraries Users List
Subject: Re: Problem with empty key word on a collection.
On Thursday, February 13, 2003, at 05:04 PM, Pierre Delisle wrote:
The change
I'll bite. What's the Unstandard Taglib? Is there a website for this?
-Original Message-
From: O'brien, Tim [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 14, 2003 11:45 AM
To: 'Tag Libraries Users List'
Subject: RE: Problem with empty key word on a collection
, 2003 11:45 AM
To: 'Tag Libraries Users List'
Subject: RE: Problem with empty key word on a collection.
-Original Message-
From: James Cook [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 14, 2003 8:17 AM
To: Tag Libraries Users List
Subject: Re: Problem with empty
Not surprised at that - a prior company I worked at, where I first
learned Java, they had consultants and (i thought..) smart engineers
working together to develop a quite large web application. The company
folded a year later, and I moved on. It wasn't till after I got into
jsp/servlets
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
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
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?
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
13 matches
Mail list logo
