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 on a collection. > > > 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 scriptlet debugging code. > > > > What exactly does empty check to determine if a collection is empty or > > not? It looks like that "empty" is checking if the folder.content is > > null or not, not if its size is zero. > > > > Folder.getContent() returns a type of java.util.Collection. > > The 'empty' operator is specified to work with java.util.List and > java.util.Map (as well as arrays and strings), not java.util.Collection in > general. > > -- > Shawn Bayern > "JSTL in Action" http://www.manning.com/bayern > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
