I apologize in advance if this isn't relevant because I've only been half paying attention to this thread....
For iBatis files other than the sql map that has to be in web.config, we include all files (the mapping and provider file) under a namespace in the project and mark them as embedded resources for compile and configure the iBatis files appropriately for embedded resources vs. separate files. This gets them into source control with our project and is also a few less files to deploy and for an admin to accidentally "tweak" when things aren't working. Not sure if that works for you or not. -----Original Message----- From: Juan Pablo Araya [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 11:19 AM To: user-cs@ibatis.apache.org Subject: Re: iBATIS looking on the wrong place for SqlMap.config SOLVED (for a part) Sorry don't know how to face that. As far as I know when you debug your application the console app search for these files; now when you are ready with the project, it searches the sqlmap in the root there is the .exe executable. It's the same when you debug because the debugger searches for the root in the application that is stored in that directory. Sorry :-( 2008/4/21 Pieter Baele <[EMAIL PROTECTED]>: > I know, there was a small syntax fault. Thx for your help! > The only problem left is that I want to place the files in some other > directory the bin/Debug, > these files are not commited to my subversion server by visual svn so I > need to store them elsewhere. > > > Pieter Baele > [EMAIL PROTECTED] > > Adrian Holovaty: "Having Python produce JavaScript is like using a > motorized wheelchair because you're too lazy to walk." > > > > > On 21 Apr 2008, at 16:43, Juan Pablo Araya wrote: > > > You have to add the MySql.Data reference in your web and test > > projects. > > > > -------------------------------------------------------- Princeton Retirement Group, Inc - Important Terms 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. 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. 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. --------------------------------------------------------
