Seam or Spring

There are so many frameworks!! What is the benefit of Seam over Spring. Or is it just JBoss/JSF specific?

I haven't used Spring till now. But SEAM makes your task very simpler. Saves time, as it does integration by itself. You just need to focus on your Business logic and UI

Hi Rakesh,

Spring is also geared to the same direction: to concentrate more over the Business logic and UI and worry less about the configuration (convention over configuration is what they call)

I want to understand what is the use of so many frameworks around. Or are we all beating around the same bush?

Hi Vyas,

I'm sure you must have gone through the net for both the technologies.
Both technologies provide integration, AOP and ease.

The major difference is Seam is more geared towards Stateful architecture while Spring is more suitable for Stateless.
Also the EJB3 support in Seam is a major reason to consider the framework.
Seam is based on EJB3 and JSF - the two technologies from Sun. And seam is also being promoted as Web-beans.

Each framework has its pro's and con's. You need to evaluate the framework based on your needs.

Thanks Padmarag

Comparing similar features offered (like remoting, persistence etc), my vote is for Seam. But if you want a wider integration with other frameworks and a better documentation it should be Spring (may be till Seam gets more documentation and how tos). But if you are not under pressure to meet a strict deadline Seam is the way to go.