What\'s your choice? Do You have any suggestions and experience?
I\'m developing an application with Hibernate 3.5 and Spring 3.0
Pros:
EclipseLink runs perfectly fine without the Weaver and equally well in Jetty, Tomcat or an OSGi platform. The standard download is a simple eclipselink.jar. Did you perhaps download the OSGi bundles by mistake?
The Weaver is not required but it will add some performance benefits and if you do no want to configure it to run in Spring you could use the static weaver at compile time ( http://wiki.eclipse.org/Using_EclipseLink_JPA_Extensions_%28ELUG%29#To_Configure_Static_Weaving_for_JPA_Entities ).
I'd say it depends on your application. If you age going to use a lot of Oracle-related features (like, you need hints in your SQL or hierarchical queries or so on), EclipseLink is more suitable for you. In other case pick up Hibernate. More details you can find at http://simpletoad.blogspot.com/2012/11/what-u-must-know-about-eclipselink-orm.html BTW, don't care about performance benchmarking there ORM - if performance is critial for - don't use ORM at all