Having noticed that over 50% of the posts in the Data Access Forum alone deal with Hibernate, I'm wondering if most of the Spring users see an overwhelming advantage of doing O/R mapping. Assuming that's true, let's back up a bit. It reminds me of the beginning of J2EE and everyone wanted to write entity beans.
Is there an O/R feeding frenzy? Having spent the last two years involved with a project that accesses a hierarchical database in a relational fashion, there is a huge impact that comes with short-circuiting what a DMBS brings to the table.
I assume that those doing O/R Mapping would prefer an Object DBMS, yet the lack of such a thing in the mainstream tells me that sufficient justification for one to convince stakeholders of the advantages doesn't exist. The advantages of Spring by removing the requirement of using EJBs is quite apparent. Rod, et. al, have given us a rich set of JDBC helpers and I would like to think they're there for more reasons than "completeness" or backward-compatibility. I did not get the impression from Rod's books that O/R is the holy grail, so what do the Hibernate users see as the great benefit? Have we set the cart before the horse or created a solution looking for a problem or are there 10% of the Spring users using Hibernate and having nothing but problems with it?
Is (and should) O/R mapping be the architectural giant it appears to be?