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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
