Spring makes it incredibly easy to work with hibernate, if you want to switch to jdo or ejb3 at a later stage it makes it as easy as it could possibly be.
There is a page on the hibernate site on the topic. http://www.hibernate.org/110.html It also allows you to remove all your transaction code from your classes and specify it in the xml file ( using wildcards ) Incidentally EJB3 is going to be largely based on hibernate and sun have already signaled their intention that JDO and EJB are going to be dropped and a new standard created most likely playing catchup with Hibernate. Using JDO just because it is a "standard" is a bad idea, I've been there before and have difficulty trusting anything that gets designed by some self interested group of big companies, usually so they can make sure that your code only works with their libraries or IDE or app server because at the end of the day you usually have to do something that ties you to their implementation. Runtime bytecode enhancement via cglib etc is the name of the game, having to add another pre-processing stage to your development cycle ( as you must do with most implementations of jdo is soooo 2002 ). Another thing EJB3 makes heavy use of IOC ( playing catchup with .NET in this regard ), if you don't "dig" IOC yet you need to start getting a handle on it and Spring is probably the best way to do this. Another thing .. once your using springframework with Hibernate for a while you will sooner or later start asking yourself another question ... I'll leave it up to you to figure out what it is. Bonne Chance Bryan > To bryan : spring/hibernate > What's the added value with spring? Have you got an article or an > example about that ? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
