Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [beanutils] problem with PropertyUtils.getNestedProperty(Object,
 name)  throwing too many IllegalArgumentExceptions
Date: Fri, 9 May 2003 11:53:37 +1000
Message-ID: <088AED8CEAB47C4E8FB3EA0465FABF00C8DF5A@chqmail2.lands.resnet.qg>
Thread-Topic: [beanutils] problem with PropertyUtils.getNestedProperty(Object,
 name)  throwing too many IllegalArgumentExceptions
Thread-Index: AcMVzc6miwkiwOTTQ8axGdqua8wXVQ==
From: "Tolley Shorn" <Shorn.Tolley@nrm.qld.gov.au>
To: <commons-user@jakarta.apache.org>

Hi folks,

Please let me know if I should be posting this message to a different place.

I have a problem with the PropertyUtils.getNestedProperty(Object, name) met=
hod.

It documents that it throws an IllegalArgumentException "if a nested refere=
nce to a property returns null".
Which is great, because I want to actually trap that exact situation and de=
al with it explicitly.
Unfortunately, the method throws IllegalArgumentException  for a number of =
other situations.  Also, because it's a runtime exception I have to assume =
that exception could be thrown from anywhere in the call stack.

Is there another way to do what I want to do without deplicating the code o=
f the getNestedProperty() method?

Currently, I'm building my own beanutils jar, and having the getNestedPrope=
rty() method throw an explicitly created subclass of InvocationTargetExcept=
ion (NullNestedReferenceException) that I can catch in my calling code.

I'd like to use an official build of beanutils though (rather than my own o=
ne).
If there's not a better way to do what I want, how do I go about requesting=
 that this functionality be added to CVS (possibly with my own patch if the=
 developers find it acceptable)?

Thanks,
Shorn Tolley.


************************************************************************
The information in this e-mail together with any attachments is
intended only for the person or entity to which it is addressed
and may contain confidential and/or privileged material.

Any form of review, disclosure, modification, distribution
and/or publication of this e-mail message is prohibited. =20

If you have received this message in error, you are asked to
inform the sender as quickly as possible and delete this message
and any copies of this message from your computer and/or your
computer system network. =20
************************************************************************