Only reason for prefering Spring-Hibernate -Spring (Hibernate template) does a good job of mapping the lousy Hibernate Exception into more developer-friendly heirarchy of more meaningful exception types.
Ditto for JDBC template ( used for simple Non-ORM DB access). Takes away the pain of SQLException and vendor-specific error codes.
I am surprised that more than 20% still use JDBC. I'm just hoping they use it for Reporting Tools, for summarizing data (group by, sum(), avg() etc.) or such areas left uncovered by the ORM tools (AFAIK).
JDBC is just too heavy and tedious for simple DB access needs. Time someone gave a serious thought to introducing LINQ in Java? |
java.net RSS Feeds
