Comments on: Do you have an impedance mismatch problem? Users speak up! Second series of user reports published. Trends and Information on Big Data, New Data Management Technologies, Data Science and Innovation. Tue, 20 Dec 2016 11:47:00 +0000 hourly 1 By: Roberto V. Zicari Thu, 02 Oct 2008 05:17:53 +0000 Hi Immo
in fact, we had a detailed discussion on this issue in two articles I published:

Java Object Persistence: State of the Union PART II
with Jose Blakeley (Microsoft), Rick Cattell (Sun Microsystems), William Cook (University of Texas at Austin), Robert Greene (Versant), and Alan Santos (Progress).


Java Object Persistence: State of the Union I
with Mike Keith: EJB co-spec lead, main architect of Oracle Toplink ORM, Ted Neward: Independent consultant, often blogging on ORM and persistence topics, Carl Rosenberger: lead architect of db4objects, open source embeddable object database, and Craig Russell: Spec lead of Java Data Objects (JDO) JSR, architect of entity bean engine in Sun’s appservers prior to Glassfish

I`d be interested to learn your opinion on that…

Best Regards

By: Immo Hüneke Fri, 26 Sep 2008 02:06:56 +0000 Having read through these user reports, which I find genuinely informative, I am surprised that nobody has pointed out a major shortcoming of Object-Relational Mapping (ORM) products such as Hibernate and its descendant, JPA: because they are designed to be portable across many different relational DBMSs, they cannot handle proprietary extensions to standard SQL, and in particular, cannot exploit the power of stored procedures, which are not compatible across different RDBMS. In many environments, stored procedures are mandated as a way for Web applications to access data – for various reasons, including security (no possibility of SQL injection attacks). Zühlke and its customers have had very good experiences with the Spring JDBC support ( for both stored procedure access and ORM.