Oops, sorry if I double-posted -- I thought my original post bounced due to
a missing subject.

Interesting, thanks Scott.


-----Original Message-----
From: resin-interest-boun...@caucho.com
[mailto:resin-interest-boun...@caucho.com] On Behalf Of Scott Ferguson
Sent: Friday, February 06, 2009 3:32 PM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Resin 3.0/3.2 Inconsistency

On Feb 6, 2009, at 1:21 PM, Aaron Freeman wrote:

> Under Resin-3.0.x the following code works whether I pass in a  
> 'email' param
> or not.  However on Resin 3.2.1, which I just installed .. It throws  
> an
> exception if an 'email' param wasn't passed in. However it works  
> great if I
> do pass an email param in.  Any thoughts?

Unfortunately, that exception is required by the JSTL specification,  
and Resin 3.2 is stricter about spec compliance.

-- Scott

> <c:set var="email" value="${param.email}"/>
> <c:set var="password" value="${param.password}"/>
> <x:forEach select="$doc/users/user[email = $email and password =
> $password]">
>       <c:set var="found" value="true"/>
> </x:forEach>
> The work around is to put a <c:if> test around the <x:forEach> and  
> test if
> param.email is defined, but I am curious if the forEach should throw  
> an
> exception when the $email variable is empty?
> Thanks,
> Aaron

resin-interest mailing list

Reply via email to