If you are taking an existing project, or a project where the business model is more important than the database model, then Hibernate would do better. Basically it boils down to how you program.
For a nice comparison of the different persistence layers, you can look here...
http://www.rollerweblogger.org/page/roller/20021013
For an example that shows the different tools in action (like AppFuse for ORMT) you can check out...
http://ortools.warneronstine.com/
How this all applies to Spring, I'm not too sure - but Torque's classes are independent of any framework so I don't see where you would have any problem.
Robert Bowen wrote:
I would be interested in this as well. It seems that the "latest and greatest" data object mapping + framework solution is Hibernate + Spring.
... which begs the question(s) - what does Hibernate do better than Torque? I am going to buy the new Manning book "Spring in Action" which talks a lot about Hibernate and Spring but I thought I might ask the list as well ...
syg
--- Johan Andries <[EMAIL PROTECTED]> wrote:
---------------------------------------------------------------------Hello,
Has anyone ever done a successful attempt on
integrating the generated Torque Java classes in the Spring framework? I've
searched the mailing list archive and found no references to this.
Kind regards, Johan
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
