What is the difference between Spring, Struts, Hibernate, JavaServer Faces, Tapestry?

Question

May I know what is the difference between:-

1. Spring
2. Struts
3. Struts 2
4. Hibernate
5. JavaServer Faces
6. JavaServer Pages
7. Tapestry

Are these technologies/framework complementary to each other? Or they are alternatives to each other (after I use one of them, then I don't need to use the other)?

Thanks.

Solution 1

1. Spring is an IoC container (at least the core of Spring) and is used to wire things using dependency injection. Spring provides additional services like transaction management and seamless integration of various other technologies.
2. Struts is an action-based presentation framework (but don't use it for a new development).
3. Struts 2 is an action-based presentation framework, the version 2 of the above (created from a merge of WebWork with Struts).
4. Hibernate is an object-relational mapping tool, a persistence framework.
5. JavaServer Faces is component-based presentation framework.
6. JavaServer Pages is a view technology used by all mentioned presentation framework for the view.
7. Tapestry is another component-based presentation framework.

So, to summarize:

• Struts 2, JSF, Tapestry (and Wicket, Spring MVC, Stripes) are presentation frameworks. If you use one of them, you don't use another.
• Hibernate is a persistence framework and is used to persist Java objects in a relational database.
• Spring can be used to wire all this together and to provide declarative transaction management.

I don't want to make things more confusing but note that Java EE 6 provides modern, standardized and very nice equivalent of the above frameworks: JSF 2.0 and Facelets for the presentation, JPA 2.0 for the persistence, Dependency Injection, etc. For a new development, this is IMO a serious option, Java EE 6 is a great stack.

See also

• Choosing a Java Web Framework now?
• Java - JDBC alternatives
• JEE6 vs. Spring 3 stack
• What to learn for making Java web applications in Java EE 6?

Solution 2

Generally...

Hibernate is used for handling database operations. There is a rich set of database utility functionality, which reduces your number of lines of code. Especially you have to read @Annotation of hibernate. It is an ORM framework and persistence layer.

Spring provides a rich set of the Injection based working mechanism. Currently, Spring is well-known. You have to also read about Spring AOP. There is a bridge between Struts and Hibernate. Mainly Spring provides this kind of utility.

Struts2 provides action based programming. There are a rich set of Struts tags. Struts prove action based programming so you have to maintain all the relevant control of your view.

In Addition, Tapestry is a different framework for Java. In which you have to handle only .tml (template file). You have to create two main files for any class. One is JAVA class and another one is its template. Both names are same. Tapestry automatically calls related classes.

Solution 3

You can see the overview and ranking for yourself here. Hibernate is an ORM, so you can use either struts+Hiberante or spring+hibernate to build a web app. Different web frameworks and many are alternatives to each other.

Solution 4

Spring is an application framework which deals with IOC (Inversion of Control).

Struts 2 is a web application MVC framework which deals with actions.

Hibernate is an ORM (Object-Relational Mapping) that deals with persistent data.

Solution 5

In short,

Struts is for Front-end development of website

Hibernate is for back-end development of website

Spring is for full stack development of website in which Spring MVC(Model-View-Controller) is for Front-end. ORM, JDBC for Data Access / Integration(backend). etc

View more solutions

Comments

[MetroidFan2002]

I'd like to point out that in this sort of comparison context some people also use the word Spring to refer to its own MVC framework (which is much nicer than Struts IMO).

[0xC0DED00D]

Nicely explained, but still it's too technical. I'd advise you to explain it in layman term. Anyways the links at the end did that.

[Wouter]

The answer is a great starting point indeed, but could be improved upon by explaining the main concepts introduced (request based vs component based frameworks, IoC containers, Presentation vs persistence framework... ) As it stands now, it requires a lot of additional googeling, but it is still a good answer, and great starting point! Upvote.