Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <20040901200053.90968.qmail@web52508.mail.yahoo.com>
Date: Wed, 1 Sep 2004 13:00:53 -0700 (PDT)
From: Kyle Miller <k@kylemiller.com>
Reply-To: k@kylemiller.com
Subject: [DBUtils] BeanProcessor enhancement request
To: commons-dev@jakarta.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

I have a JavaBean that needs to be populated from 3
different select statements, unfortunately DBUtils
BeanProcessor doesn't support the reuse of beans, it
instantiates a new instance each time.

I would like to see more of the methods in
BeanProcessor be protected instead of private.  I like
the JavaBean processing in BeanProcessor, and I don't
want to reimplement it.  However I would like to
override the newInstance method to return an existing
object instead of new instance.  I can also think of
instances where someone may want to override the
isCompatableType method.

I have implemented a BeanReuseProcessor that works
with a single bean or a list of beans, and it is fully
junit tested.  It required changing the visibilty of
BeanProcessor.newInstance(...) to protected, so I
would like to get the changes added to CVS so I don't
have to keep hacking the source every for every
release.

I think this is a useful enhancement, and I would like
to contribute it to the project.  Please let me know
what you think.

-- Kyle


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