hi, i hear that hibernate is good to use for replacing normal jdbc query ...can anyone comments this ?
we are currently starting a new project which is based on j2ee , some of the staff are suggest hibernate , but our team don't have many people know this technology , is this technology worth to replace jdbc query ?
I'm currently reading "Hibernate - a developer's notebook". And I have to say that Hibernate looks pretty good. I think if I were starting a new project, I would seriously consider using something like Hibernate.
The best place for more info is probably the Object-Relational Mapping subforum. There have been lots of discussions of the merits of Hibernate and other ORM tools recently.
The simple answer is: yes, learn Hibernate. It has good prospects - and EJB 3.0 will future-proof it for the near future.
The technology has clear market momentum - and there's clear market signs that the vendors of proprietary ORM products and also data persistence runtime product vendors with deployment fees are begining to panic.
One issue is that you do need to deal with is the steep learning curve. CodeFutures expects to be making an announcement in the near future that should help a lot with this issue. Stay tuned!
Another option is learning JDO rather than (or as well as) hibernate.
JDO queries are expressed in a syntax much like ordinary Java, so it's easy to do basic stuff really quickly, and then learn more of the intricacies (caching, disconnected object graphs, etc) as you go.
Both JDO and hibernate are about 90% of the same as the forthcoming EJB 3 POJO persistence. The main difference of course is that hibernate is a proprietary API implemented only by a single vendor, whereas there are a few dozen JDO vendors, including some pretty good free & open source implementations.
So JDO will more than likely be a better investment of time and effort learning, since there are plenty of JDO vendors to maintain compatibility with the JDO APIs and Spec, whereas developing against hibernate APIs will probably mean you'll *have* to migrate to EJB 3 in the future. Most JDO vendors on the other hand, will give you the *option* of migrating to EJB 3, by supporting both JDO 2 and EJB 3 persistence within the same product.
Dave Clark<br />Senior WebSphere Architect<br /><a href="http://www.versant.com" target="_blank" rel="nofollow">Versant Open Access - JDO2 & EJB3</a>