Let's assume we end up with several db-to-atom adapters based on several
mapping layers, say raw jdbc, ibatis, and hibernate. What should the
names of the various adapters be? At a high enough level, they all do
the same thing: adapt data from a database. In theory, each could exist
within a single package, but they certainly need to have
implementation-specific class names.
- James
David Primmer wrote:
I have an objection to this. It focuses too much on implementation details.
I'd prefer to go the other way towards a name that describes what it does,
not how it does it. You're not adapting iBatis, you're adapting data from a
database. There must be another way to say this. The package namespace seems
to make sense but not the class name.
davep
On Feb 12, 2008 5:11 AM, David Calavera <[EMAIL PROTECTED]> wrote:
Hi,
I've seen JdbcCollectionAdapter depends on IBatis and I think the name is
ambiguous when I read "Jdbc" I think on a native jdbc connection to the
database without orms. I think we should rename this class to
IBatisCollectionAdapter and move it to some other package like "
org.apache.abdera.protocol.server.adapters.orm.ibatis".
Unless you have no problem, I'm going to create the jira issue and submit
a
patch.
Btw, I'm thinking on create an HibernateCollectionAdapter XD.
Cheers
