Originally posted by Anh Vu: Hi all, I want to learn about web framework . I dont know Struts and dont know Spring . Where should I begin ? Do I must learn Struts first , then learn Spring ?
Struts is a web framework; Spring is a dependency injection framework. Two very different things. Spring is bigger and more inclusive than Struts.
How well do you know Java and web development in general? Have you written and deployed Java web apps? Do you know servlets and JSPs well? If so, there's an advantage to going with Spring. It'll do more for you than Struts.
One other point to consider: Struts isn't being developed anymore. It's considered "mature", and the developers have moved on to other technologies like Java Server Faces. Spring is still quite active, so you might be better off going with Spring.
But be warned - Spring is bigger and different from what you're used to. Start with the on-line tutorial (Spring MVC step by step) and see what you think. If you like it, get a good book to act as your guide. (e.g., "Pro Spring" or "Spring in Action")
Spend some time learning both..take up whichever u feel comfortable with..I guess you meant Spring MVC in spring..Spring would be really interesting if you can learn hibernate as well. oh by the way struts is on its way out..but doesnt hurt to learn.. will help u in analysing how different frameworks work..will help u one day when u become an architect
If Java had true garbage collection, most programs would delete themselves upon execution -- Robert Sewell
If you are going to learn a new framework, learn Tapestry. It rocks!
posted 14 years ago
Thanks all very much . Uhm , I have another question . I have heard about Ruby on Rails . Would you like to compare Ruby on Rails with some Java frameworks ?
posted 14 years ago
Originally posted by Anh Vu: Thanks all very much . Uhm , I have another question . I have heard about Ruby on Rails . Would you like to compare Ruby on Rails with some Java frameworks ?
I'll confess before I start that I've only a reading knowledge of Ruby and Ruby on Rails.
As I understand it, Ruby on Rails helps to do "typical" problems (e.g., exposure of relational data in a web browser) easily. Instead of getting out the big JEE hammer, it's possible to accomplish problems like webifying data more in the manner that Microsoft developers are used to.
There's nothing like a JEE container to worry about starting and stopping.
It'd be worth knowing, in my opinion. It's a goal of mine for 2006.
I miss the old days when I would think up a sinister scheme for world domination and you would show a little emotional support. So just look at this tiny ad: