Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 356 invoked from network); 8 Apr 2003 11:41:20 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 8 Apr 2003 11:41:20 -0000 Received: (qmail 16449 invoked by uid 97); 8 Apr 2003 11:43:11 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org Received: (qmail 16442 invoked from network); 8 Apr 2003 11:43:10 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 8 Apr 2003 11:43:10 -0000 Received: (qmail 97803 invoked by uid 500); 8 Apr 2003 11:40:51 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 97770 invoked from network); 8 Apr 2003 11:40:50 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 8 Apr 2003 11:40:50 -0000 Received: (qmail 16422 invoked by uid 50); 8 Apr 2003 11:42:41 -0000 Date: 8 Apr 2003 11:42:41 -0000 Message-ID: <20030408114241.16421.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 18791] - BeanComparator should handle null property values (?) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18791 BeanComparator should handle null property values (?) ------- Additional Comments From epugh@upstate.com 2003-04-08 11:42 ------- When I originally wrote the BeanComparator, I had that type of functionality, but it was removed for the initial commit because of exactly that issue. Who comes first, the null or the not null value? To get around this, I wrote a NullComparator that allows you to specify who comes first, the null or the not null value. I then wrapped the bean comparator in the null comparator using the comparatorChain. I think add this functionality directly confuses the BeanComparator. And also, you could argue other comparators suffer from the same issue with nulls. If you want to see some code, let me know. Eric --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org