If you have no idea what Hibernate is and you want to learn Spring MVC with Hibernate, then it's a good idea to first at least have an idea what Hibernate is.
Hibernate is an ORM (Object-Relational Mapping) framework: it helps you to map Java classes to and from database tables in a traditional relational database.
Spring is a great, but huge framework that supports many different Java technologies. To learn the basics of Spring (dependency injection, etc.) you'll have to know Java, but not really much else. To understand why Spring does things the way it does, it's good to have some understanding of the basic principles and best practices of designing software, of which design patterns are a part.
Haritha jayathunga wrote:thanks. So isn't there any need to learn sevelets, J2EE at all?
No idea. Does your company use them?
what about some J2EE techs like sessions, cookies etc. ?
I think you're obsessing too much about "buzzwords". You may or may not need any or all of these things, depending on where you work (or intend to work).
My advice would be to follow Jesper's: Learn the basics really well; all the other stuff - including Hibernate - are just frameworks written in Java that help you manage the complexities of things like databases and Web-based projects. Other than that, the only thing I can suggest is: tackle ONE thing at a time.
J2EE (actually called JEE now) is probably going to take you at least 6 months to get competent with; and probably the same for Spring, so take it slow.
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
posted 5 years ago
sure I will do that. thanks Jasper and Winston!!
We can fix it! We just need some baling wire, some WD-40, a bit of duct tape and this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!