Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 22925 invoked from network); 12 Mar 2004 21:51:07 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 12 Mar 2004 21:51:07 -0000 Received: (qmail 80082 invoked by uid 500); 12 Mar 2004 21:50:51 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 79833 invoked by uid 500); 12 Mar 2004 21:50:49 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 79815 invoked from network); 12 Mar 2004 21:50:49 -0000 Received: from unknown (HELO web60805.mail.yahoo.com) (216.155.196.68) by daedalus.apache.org with SMTP; 12 Mar 2004 21:50:49 -0000 Message-ID: <20040312215054.64446.qmail@web60805.mail.yahoo.com> Received: from [64.32.141.21] by web60805.mail.yahoo.com via HTTP; Fri, 12 Mar 2004 13:50:54 PST Date: Fri, 12 Mar 2004 13:50:54 -0800 (PST) From: David Graham Subject: Re: [mapper] Any implementations yet To: Jakarta Commons Users List In-Reply-To: <1079119121.3903.17.camel@trout> 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 --- "John E. Conlon" wrote: > On Fri, 2004-03-12 at 11:04, David Graham wrote: > > --- "John E. Conlon" wrote: > > > Mapper looks like a nice solution to debundle mapping > implementations > > > but are there any implementations using Mapper right now. > > > > > > I would like to use this even if I have to write wrappers myself, > but I > > > don't want to re-invent the wheel. > > > > Each implementation of the Mapper interface will typically persist one > > kind of business object. > Ah I think I see said the blind man. > > > Obviously this is specific to your app. so I > > don't know what you mean by your question. > > > > >From the introduction: > > The purpose of Mapper is similar to Commons Logging. It isn't a mapping > technology itself, it merely exposes common functionality of other > mapping APIs. > > I was expecting there may be mapper wrappers for some of the persistent > technologies out there... Mapper used to contain JDBC helper code but that was removed when DbUtils was released. > > What else do you have planned for the Mapper project besides > documentation? Much of the most useful code has migrated to other projects (ie. DbUtils) and what remains is a small layer above mapping technologies. I've been considering changes to the Mapper interface and exception handling but Mapper needs a bigger community before it can be released to commons proper. Feel free to contribute code/ideas! David > > thanks, > John > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-user-help@jakarta.apache.org > __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org