Use useStatementNamespaces="true" in sqlMap.config and then correct the
<sqlMap namespace="TheNamespaceName"
propertie under each xml.
The use of iBatis now is like
mapper.Instance().Queryfor<>("Namespace.Statement",parameters);
We use iBatis 1.6.2 with this and never see that problem.
Greetings and sorry for my poor english!
2010/4/14 danw123 <[email protected]>:
>
> We have two data definition files in the same directory for different stored
> procedures. Each of these files contains:
>
> <parameterMap id="select-param" class="int">
>
> Thus, we have parameter maps with the same name, but in different files.
>
> iBatis DataMapper 1.5.1 did not have a problem with this. We are trying to
> upgrade to iBatis DataMapper 1.6.1 and we are finding that the wrong
> parameterMap is being used for the stored proc (from another file).
> It seems like iBatis is using the first parameterMap it finds with the
> correct name, regardless of what file its in.
>
> We are embedding the data definition files in the assemblies.
>
> Has any else observed this in iBatis DataMapper 1.6.1 and is there a
> workaround?
>
> --
> View this message in context:
> http://old.nabble.com/paramaterMaps-with-identical-names-getting-mixed-up-between-files-tp28249052p28249052.html
> Sent from the iBATIS - User - Cs mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Juan Pablo Araya
787 76 034
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
