I don't think schemas for the config and mapping files will ever be 100% identical between the Java and .Net version of iBATIS. As I mentioned in a post earlier today, Java has attributes like jdbcType that simply aren't available in .Net. .Net also has things like the listClass attribute that aren't available in the Java version becuase strongly typed collections aren't as prevalent as they are in .Net.
Regarding ComplexType mappings, are you referring to this thread: http://www.mail-archive.com/[email protected]/msg00321.html I think Java style complex type mappings would be nice. I think the Java dynamic sql tags have a prePend attribute available. Do you know of any other differences? I think people would appreciate a wiki entry discussing the differences between the Java and .Net versions helpful. --- Okku Touronen <[EMAIL PROTECTED]> wrote: > Hello I am running iBatis in .NET 2.0 framework. I have tried both > the > binary release and compiled my own from the SVN. > > Since iBatis is designed for 1.1 some cool features as Nullable types > are > not included by default. But it is easy to extend with TypeHandler > extensions. > > The problems I have run into stem from that the .Net version is not > SqlMap > compatible with the java version. Can't remember all stuff but here > are some > from top of mind: > * ComplexType in result maps must use the resultMapping design > * New schema for the sqlmap.config > * Some new syntax for dynamic SQL > > /Okku > > -----Original Message----- > From: oleksa borodie [mailto:[EMAIL PROTECTED] > Sent: den 27 september 2005 16:24 > To: [email protected]; Clinton Begin > Subject: Re: Will iBATIS work with Framework 2.0? > > On 9/27/05, Ron Grabowski <[EMAIL PROTECTED]> wrote: > > > Did you search the list archives? > > http://www.mail-archive.com/user-cs%40ibatis.apache.org/ > > Someone asked a very similiar questions 24 hours ago. > > You mean "logging in ASP.NET 2.0" thread > (http://www.mail-archive.com/user-cs%40ibatis.apache.org/msg00335.html)? > I saw this thread but it is not about framework 2.0 - it's about > logging AFIAU. > > > When the NUnit tests failed did you get any kind of error message? > > I couldn't load IBatisNet.Test.dll in the standart NUnit 2.2.0 - it > says that dll format is invalid. I''ve compiled NUnit 2.2.2 with VS > 2005 but it fails to test any *.nunit project :( > But I could run NUnit test via Visual studio add-on called > ReSharper. > It says that "DaoManager couldn't configure providers. Provider > named > ByteFx ot found, failed. Cause couldn't load fle or assembly > ByteFX.MySqlClient ..." > I've added > <provider > name="sqlServer2" > description="Microsoft SQL Server 7.0/2000 provider in > framework .NET V2" > default="true" > assemblyName="System.Data, Version=2.0.0.0, Culture=neutral, > PublicKeyToken=b77a5c561934e089" > connectionClass="System.Data.SqlClient.SqlConnection" > commandClass="System.Data.SqlClient.SqlCommand" > parameterClass="System.Data.SqlClient.SqlParameter" > parameterDbTypeClass="System.Data.SqlDbType" > parameterDbTypeProperty="SqlDbType" > dataAdapterClass="System.Data.SqlClient.SqlDataAdapter" > > commandBuilderClass="System.Data.SqlClient.SqlCommandBuilder" > usePositionalParameters = "false" > useParameterPrefixInSql = "true" > useParameterPrefixInParameter = "true" > > parameterPrefix="@" > /> > > to the providers.config and changed > <provider name="sqlServer2"/> in the dao_MSSQL_SqlClient.config > In the IBatisNet.Test.dll.config I've uncommented > <add key="database" value="MSSQL"/> > <add key="providerType" value="SqlClient"/> > > > Perhaps you can put together a .Net 2.0 migration guide once you > get > > things working correctly on your system. > > I cann't write such guide because will start new project for 2.0 > > Good bye. > > > >
