From user-cs-return-2367-apmail-ibatis-user-cs-archive=ibatis.apache.org@ibatis.apache.org Mon May 21 11:31:00 2007 Return-Path: Delivered-To: apmail-ibatis-user-cs-archive@www.apache.org Received: (qmail 51938 invoked from network); 21 May 2007 11:31:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 May 2007 11:31:00 -0000 Received: (qmail 76626 invoked by uid 500); 21 May 2007 11:31:05 -0000 Delivered-To: apmail-ibatis-user-cs-archive@ibatis.apache.org Received: (qmail 76387 invoked by uid 500); 21 May 2007 11:31:04 -0000 Mailing-List: contact user-cs-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-cs@ibatis.apache.org Delivered-To: mailing list user-cs@ibatis.apache.org Received: (qmail 76376 invoked by uid 99); 21 May 2007 11:31:04 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 04:31:04 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [199.43.64.2] (HELO mlnyc902er.ml.com) (199.43.64.2) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 04:30:56 -0700 Received: from MLNYC855BH.amrs.win.ml.com (unknown [141.128.12.205]) by mlnyc902er.ml.com (Postfix) with ESMTP id E99435422B for ; Mon, 21 May 2007 07:30:32 -0400 (EDT) Importance: normal Priority: normal Received: from mlnya301bh.amrs.win.ml.com ([170.240.239.46]) by MLNYC855BH.amrs.win.ml.com with Microsoft SMTPSVC(5.0.2195.6920); Mon, 21 May 2007 07:30:26 -0400 Received: from MLNYC728MB.amrs.win.ml.com ([141.128.12.73]) by mlnya301bh.amrs.win.ml.com with Microsoft SMTPSVC(5.0.2195.6920); Mon, 21 May 2007 07:30:15 -0400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: DAO with SQLMAP vs just SQLMAP Date: Mon, 21 May 2007 07:30:14 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: DAO with SQLMAP vs just SQLMAP thread-index: AceaLBdK9m1xWa74TkOqiZKHLRxNWwBbw5Qg From: "Clough, Samuel \(USPC.PRG.Atlanta\)" To: X-OriginalArrivalTime: 21 May 2007 11:30:15.0446 (UTC) FILETIME=[670C8B60:01C79B9B] X-Virus-Checked: Checked by ClamAV on apache.org Sounds like overkill to me. Just using iBatis gives you great flexibility with your dao if implemented properly. If you truly need something more independent, you'll probably want an IOC/DI container like another lister mentioned. Also, the iBatis DAO is deprecated in the since that no new development is ongoing at this point (presumably because of the other container based solutions like spring.net/castle, etc)=20 -----Original Message----- From: Garth Keesler [mailto:garthk@gdcjk.com]=20 Sent: Saturday, May 19, 2007 11:40 AM To: iBatis Net Subject: DAO with SQLMAP vs just SQLMAP I'm building an app using SQLMAP but I keep reading about DAO and wonder if I should be using it as well. The app is pretty straightforward, running against a single SQL Server 2005 database with all access to the database via the classes and SQLMAP. Given this relatively simple config, are there any compelling reasons to use DAO as well? Thanx, Garth=20 -------------------------------------------------------- Princeton Retirement Group, Inc - Important Terms=20 This E-mail is not intended for distribution to, or use by, any person = or entity in any location where such distribution or use would be = contrary to law or regulation, or which would subject Princeton = Retirement Group, Inc. or any affiliate to any registration requirement = within such location.=20 This E-mail may contain privileged or confidential information or may = otherwise be protected by work product immunity or other legal rules. No = confidentiality or privilege is waived or lost by any mistransmission. = Access, copying or re-use of information by non-intended or = non-authorized recipients is prohibited. If you are not an intended = recipient of this E-mail, please notify the sender, delete it and do not = read, act upon, print, disclose, copy, retain or redistribute any = portion of this E-mail.=20 The transmission and content of this E-mail cannot be guaranteed to be = secure or error-free. Therefore, we cannot represent that the = information in this E-mail is complete, accurate, uncorrupted, timely or = free of viruses, and Princeton Retirement Group, Inc. cannot accept any = liability for E-mails that have been altered in the course of delivery. = Princeton Retirement Group, Inc. reserves the right to monitor, review = and retain all electronic communications, including E-mail, traveling = through its networks and systems (subject to and in accordance with = local laws). If any of your details are incorrect or if you no longer = wish to receive mailings such as this by E-mail please contact the = sender by reply E-mail.=20 --------------------------------------------------------