Java O / R Level for SQL Server?

Question

I have a java server (and not a website that looks more like a large multi-threaded stand-alone application) that needs to talk to the MS SQL Server database.

I was just working on another project that ported the home O / R layer from oracle to SQL Server, and it ran into serious problems due to too many oracle assumptions (mostly blocking). So, which O / R layer should I use?

Edit: I heard about sleeping, but everything else is useful! In particular, can any of these APIs / frameworks help with the special flaws of SQL server blocking strategies in a multi-threaded environment?

Answer 1

Hibernate iBATIS. .

Hibernate:

• - .
• sql

Ibatis:

• ,
• sql

SQL Server .

Answer 2

Hibernate - . , Oracle TopLink, iBatis, , .

Answer 3

Cayenne. . . . cayenne .

Answer 4

BEA Kodo Microsoft SQL Server (, Solarmetric Kodo). , Hibernate JDO. , /.

Hibernate - . - TopLink.

, , EJB3, Java Persistance API (JPA) Java Data Objects (JDO). JPA, , , API Hibernate, JDO, Toplink, EJB3 ..

Answer 5

Sleep mode is good. But there are different options for implementing Hibernate. I suggest Hibernate 3.x (3.2?) With JPA. I also usually use Spring 2.5 as the basis for business logic. Hibernation and Spring work particularly well because they can separate name resolution domains to an extent, which reduces confusion in accessing O / R objects.