On Mon, May 13, 2013 at 4:30 PM, Emmanuel Bourg <ebo...@apache.org> wrote:
> > The advantage is an API that is cleaner and easier to understand. > I changed the methods to be package private. > As for the name, what about "SmartBeanProcessor" or > "ImprovedBeanProcessor" (much like the ImprovedNamingStrategy in > Hibernate) ? If this implementation is much better than the one in > BeanProcessor, maybe it could be merged with BeanProcessor to be used by > default? > This could be merged into the BeanProcessor by simply adding a constructor that takes a char (or array of chars) that are excluded when performing column to bean property matching. This would leave the interface to the BeanProcessor essentially the same, but add this functionality. If this is the plan though, I'd add it to both the 1.x and 2.x branches. Thoughts? Bill-
