Was coming across JBoss seam in my area of work. Which made me wonder, why to go for Seam when we have EJB 3.0? I could not find any compelling reasons or features from a beginner point of view.
I thought its good to ask out folks like you who have used it or knew the exact answer for it. I also tend to see a lot of frameworks floating around and could not draw a line of demarcation as to which one came into existence to solve what kind of problem, because I see a lot of similarities between them
And, when given a choice to choose one of these frameworks, how would we be doing it. I understand, we should be targeting on the requirements to draw our conclusions, but what if there are more than one framework which suit the requirement? What are the points or questions should be answered to favor the decision?
Thanks a lot for your time on this.
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Well, because Seam and EJB are not competing technologies.
Seam was actually started because while JSF and EJB3 was in the Java EE spec, there was nothing in the EE spec that talked about how JSF and EJB3 can talk to each other and integrate.
Seam can integrate EJB3 beans as backing beans in JSF. Then JBoss Seam added even more to it to go beyond this "glue" to even a point where you aren't tied to having to use EJB3 if you use Seam, it is just one of the options.