Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [Jelly] inconsistency in boolean handling
From: Jason van Zyl <jason@zenplex.com>
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
In-Reply-To: <1056919273.2773.93.camel@localhost.localdomain>
References: <1056919273.2773.93.camel@localhost.localdomain>
Content-Type: text/plain
Organization: Zenplex
Message-Id: <1056922354.2773.96.camel@localhost.localdomain>
Mime-Version: 1.0
Date: 29 Jun 2003 17:32:34 -0400
Content-Transfer-Encoding: 7bit

On Sun, 2003-06-29 at 16:41, Jason van Zyl wrote:
> Howdy,
> 
> I have a variable in the context that is a String and has a value of
> "true". Using <j:if/> and <j:when/> yield different results.
> 
> If ${value} is set to "true" :
> 
> <j:if test="${value}"> evaluates to false and the body doesn't run.
> 
> while
> 
> <j:when test="${value}"> evaluates to true and the body runs.
> 
> Before each of these blocks I am echoing the value of ${value} and it
> appears to be "true". From the source they they look like they are
> evaluated the same yet I am getting different results?
> 
> Anyone know of any oddities with boolean evaluation?

This is part of another more subtle error, in my <j:if/> evaluation the
body is indeed run but the body is an ant task where a NPE occurs and it
seems to get completely eaten and everything continues. So it looks like
it doesn't evaluate but does. I'll dig deeper.

-- 
jvz.

Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org