My developers are waging a civil war. In one camp, they've embraced Hibernate and Spring. In the other camp, they've denounced frameworks - they're considering Hibernate though.
The question is: Are there any nasty surprises, weaknesses or pit-falls that newbie Hibernate-Spring converts are likely to stumble on?
PS: We've a DAO library that's not very sophisticated. I doubt that it has Hibernate's richness, but it's reaching some sort of maturity (i.e. it's not been changed in the last few projects it's included).
Spring is an open-source application framework developed by pivotal which provides infrastructure support for developers and lets them concentrate on logic whereas Hibernate is an open-source, lightweight, a cross-platform framework is developed by Red Hat.
Hibernate provides Object-Relational Persistence and Query service for applications. Spring has a number of modules such as Spring core, Spring MVC, Spring Security, Spring JDBC & more. Hibernate is an ORM and does not have modules like Spring.
We can simply integrate hibernate application with spring application. In hibernate framework, we provide all the database information hibernate. cfg.
Java frameworks are specific to the Java programming language. It's a Java platform for developing software applications and Java programs. Java frameworks are bodies of reusable pre-written code acting as templates that developers can use to create applications by filling in custom code as needed.
They've denounced frameworks?
That's nuts. If you don't use an off-the-shelf framework, then you create your own. It's still a framework.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With