Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 13648 invoked from network); 7 Dec 2003 17:29:43 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 7 Dec 2003 17:29:43 -0000 Received: (qmail 62807 invoked by uid 500); 7 Dec 2003 17:29:33 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 62749 invoked by uid 500); 7 Dec 2003 17:29:32 -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 62736 invoked from network); 7 Dec 2003 17:29:32 -0000 Received: from unknown (HELO web60807.mail.yahoo.com) (216.155.196.70) by daedalus.apache.org with SMTP; 7 Dec 2003 17:29:32 -0000 Message-ID: <20031207172935.16262.qmail@web60807.mail.yahoo.com> Received: from [67.162.145.118] by web60807.mail.yahoo.com via HTTP; Sun, 07 Dec 2003 09:29:35 PST Date: Sun, 7 Dec 2003 09:29:35 -0800 (PST) From: David Graham Subject: Re: [DbUtils]Making the BeanHandler... Even Smarter To: Jakarta Commons Developers List In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I added mapColumnsToProperties to the ColumnProcessor interface. Take a look at the BasicRowProcessor.defaultProcessor implementation. Is there any value to having this implementation or should we just use BasicColumnProcessor? It seems like anyone using Oracle and number fields needs BasicColumnProcessor anyways and I don't see any backward incompatibilities using BasicColumnProcessor. David --- Corby Page wrote: > One other note. I will be perfectly happy if we just make the > mapColumnsToProperties() method protected. But I think it would be even > better if we made it a public method in the ColumnProcessor interface. > > That way, the ColumnProcessor would completely encapsulate the mapping > of > both names and datatypes from ResultSet columns to JavaBean properties. > In > my opinion, that would be a cleaner separation of concerns. > > Thanks, > Corby > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org