Multiple databases are supported by defining multiple <context> blocks.
Clinton
On 7/6/05, Mitchell, Steven C <[EMAIL PROTECTED]> wrote:
Answered my own question. I can pass the name of the various mapping config files I need in a properties file:properties.setProperty("ibatis.mapping.conf", "the file I need");return DaoManagerBuilder.buildDaoManager( reader, properties );<transactionManager type="SQLMAP" ><property name="SqlMapConfigResource" value="${ibatis.mapping.config}" /></transactionManager>-----Original Message-----
From: Mitchell, Steven C
Sent: Wednesday, July 06, 2005 7:54 AM
To: '[email protected]'Subject: RE: Multiple Database Best PracticesHow does that work? Looking at the DTD there can be only one TransactionManager. Multiple property elements are allowed, but does iBatis support multiple "SqlMapConfigResource" properties within a TransactionManager?<transactionManager type="SQLMAP" ><property name="SqlMapConfigResource" value="${ibatis.mapping.config}" /><property name="SqlMapConfigResource" value="${my.other.ibatis.mapping.config}" /></transactionManager>-----Original Message-----
From: Clinton Begin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 05, 2005 10:00 PM
To: [email protected]
Subject: Re: Multiple Database Best Practices
You're right about the multiple SqlMapConfig.xml files, but you need only one dao.xml file, as DAO supports multiple datasources.
Cheers,
Clinton
On 7/5/05, Mitchell, Steven C <[EMAIL PROTECTED]> wrote:Is there a recommended best practice for handling an application that
connects to multiple databases? Is it as simple as maintaining multiple
sets of dao.xml and sql-config.xml files?
