Just when you think you’ve got your developer tools all sorted out, a fresh crop is sure to emerge. This article uses a real-world example to introduce you to two of the most exciting new technologies for the enterprise. Hibernate is an object-relation mapping tool and Spring is an AOP framework and IOC container. Follow along as it shows you how to combine the two to build a transactional persistence tier for your enterprise applications and write code that is database-vendor agnostic, and that can run inside of a J2EE container or run standalone.
Use Java, Hibernate and Spring for Transactional Persistence
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
why is it that ibm appears to be championing Java better than sun? i don’t see sun publishing interesting articles which aim not only to introduce technologies, to debate issues, but also to get developers…. developing with java.
and this is the ibm stance that is appreciated. sun’s stance is not developer friendly. why all the effort into “sunOne studio”? developers aren’t the target for sun’s exertions.
if only ibm had invented java…
The author isn’t an IBM employee, and Developer Works isn’t a Java-specific website. Not that I don’t agree with you, but this article is not a valid example.
why is it that ibm appears to be championing Java better than sun
Is IBM making money from Java?
Yup!
Is Sun?
err…
those tools explained are great, we are actively using hibernate, i havent seen anything comparable against hibernate for the other langages on the open source arena.
I have been using Hibernate in an enterprise level project for more than a year, the results are more than satisfactory, Spring is top in my next to exlpore list, but I have to say Hibernate coupled with a sound inheritance heirarechy and a slim controller design makes for a great and fun development process
these technologies are not “standard”, yet better than the standards. Hibernate vs JDO/or Ejb. Spring vs App server specific code.
well, honestly there are also places using EJB makes sense. i do not think they clash badly..
Sometimes using IBatis instead of hibernate also may make sense. Good thing about java open source, there are usually much more than one solution for problems.
Yes these technologies are not standard in sence “JSR” but they can become quickly de facto standard. I use Spring+Hibernate in a buisness-critical project witch will be soon in production. I’m quite happy with this and i must tell :
– it save time
– it enforce good design
– it is simple to learn (if you have good OO skill)