Yes, you could open a Jira Ticket to track it even if the current version in SVN already correct it.
It has been corrected with the add of intellisense support on xml config files.
But the way if you have define a provider for Informix could you post it.
Thanks
On 7/20/05, agcunha <[EMAIL PROTECTED]> wrote:
I found the BUG.
The problem is on DAO. It's on "DomDaoManagerBuilder.cs" file.
Look at the function : private Provider ParseProvider(ConfigurationScope
configurationScope)
Line: XmlNode node =
configurationScope.NodeContext.SelectSingleNode("//database/provider");
This way, the DomDaoManagerBuilder sets the same provider (the first in
file) for both contexts (InformixMapDao and SqlServerMapDao), although
the dao.config file specifies two different providers. The datasource
configuration is right,so, I changed "//database/provider"
for "database/provider" (like the others Parse Mathods in this class).
Do you know whether It will have any impact on others Ibatis functions? I
think not...
Should I register this bug on JIRA?
Thanks,
Anderson
Em (18:44:05), [email protected] escreveu:
>Hello
>
>> 1º - I have to persist objets in TWO different databases (Informix and
SQL
>> Server)
>> 2º - I have to use TWO IBatis Mappers (Informix and SqlServer)
>> 3º - I have to use DaoManager to manage my DAO objects.
>> ex: DaoManager.GetInstance("InformixMapDAO") and
>> DaoManager.GetInstance("SqlServerMapDAO")
>
> May be such my code will help you:
>
>private static SqlMapper GetMapper(string sqlmapname)
>{
>XmlDocument document = new XmlDocument();
>document.Load(sqlmapname);
>return SqlMapper.Configure(document);
>}
>
>This is body of the function that returns SqlMapper configured by file
>that name is passed as parameter. Configuration file looks like:
>
><?xml version="1.0" encoding="UTF-8" ?>
>
>----------
