Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <525EEDD6.1000502@oliver-heger.de>
Date: Wed, 16 Oct 2013 21:49:42 +0200
From: Oliver Heger <oliver.heger@oliver-heger.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
 rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: [BeanUtils] Generics for BeanComparator
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

There is another complicated one:

BeanComparator implements Comparator in a way that it compares a given
property of a specific bean class. The actual comparison is handled by
another Comparator stored in a member field.

So I am tempted to transform it to BeanComparator<T, P> where T is the
bean class and P is the type of the property. The internal Comparator
would then be of type <P>.

However, this does not really work out for the following reasons:
- The internal comparator can be passed to the constructor, but this is
optional. If it is not defined, a helper class from [collections] is
used providing a generic Comparator on Comparable objects. How can this
be aligned to the type parameter?
- The value of the property to be compared is obtained using
PropertyUtils which returns an Object. So there is no chance for the
compiler to do type checks. Perhaps we can check manually whether the
value of the property is of the expected type, but this implies that we
have to determine the class of the type parameter at runtime. AFAIK this
is not always possible, e.g. if a subclass is created which does not
have type parameters.

Any ideas?

Thanks
Oliver


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