Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.219.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAFmzfTWkWxHia1iMkrmg671=uu9ivJrMRM-d+C0_xBxL13uLhQ@mail.gmail.com>
References: 
 <CAFmzfTWkWxHia1iMkrmg671=uu9ivJrMRM-d+C0_xBxL13uLhQ@mail.gmail.com>
Date: Wed, 10 Jul 2013 18:23:29 +0400
Message-ID: 
 <CABzHfVn4eyqvQBzympZUDAitE7er7N5AeAimaub3UUHd5GLaEg@mail.gmail.com>
Subject: Re: javax.el.ListELResolver.isReadOnly
From: Konstantin Kolinko <knst.kolinko@gmail.com>
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

2013/7/10 Violeta Georgieva <milesg78@gmail.com>:
> Hi,
>
> In the javadoc it is not described that the method throws IAE when the
> property cannot be coerced into an integer. Moreover it is specified that
> the property will be ignored by the resolver:
>
> "
> property - The index of the element in the list to return the acceptable
> type for. Will be coerced into an integer, but otherwise ignored by this
> resolver.
> "
>
> Should we return the corresponding readOnly result and not throw IAE?
>

If it is a non-integer property, just ignore it.

For example, in Javascript a list has both indexes and a "length"
property. The "length" property should be silently ignored by
ListELResolver. It is the task of other resolvers (e.g.
BeanELResolver) to handle it.

Best regards,
Konstantin Kolinko

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