Yes, I do like the service layer idea better. The only caveat is that I need a service layer class for every domain class, which could get unwieldy. We currently use an active record style approach, but I really want PI domain objects. I also loathe writing ADO.NET code. Because we use sprocs here, I figure Ibatis will remove the ado.net, while giving me PI objects. The downside is that if I want abstraction (I do), I need a service class for each domain object.
> Date: Tue, 22 Apr 2008 08:57:37 -0400> From: [EMAIL PROTECTED]> To: > [email protected]> Subject: Re: Abstracting Mappers> > On Tue, Apr > 22, 2008 at 8:48 AM, Sal Bass <[EMAIL PROTECTED]> wrote:> >> > I was curious > to know how other developers approach the issues of> > abstracting the > mappers for testing and development in general.> >> > I share your dislike of > singletons. Instead, I would recommend a> service layer that knows the > specifics of performing CRUD operations> on simple model objects. Then look > at something like spring to tie it> all together.> > Ideally only the service > layer would even know about iBatis in this> implementation. That leaves you > free to test or swap implementations,> or work around later issues with the > API.> > Sheldon _________________________________________________________________ In a rush? Get real-time answers with Windows Live Messenger. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_realtime_042008
