This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm trying to find out some information about practical use of the Seam framework. I'm interested about the pros and cons about using the Sean framework in "every day use". Which part of the Seam make him usefull tool in making software, and which part makes him useless? Are there any frameworks which are better of Seam and can be used insted of him. Which part of the Seam should be changed and in which way? I was trying to find some information about how often different people use Seam and to be honest it was very hard. People use Spring and most of them is not going to change it on the Seam. Maybe someone can answer why the Spring framework is better than the Jboss Seam at the moment. Maybe someone can answer these questions or maybe can write his opinions about the Seam, his thoughts about the JBoss Seam. I will be very gratefull for every answer about using Seam, about problems with this framework, and of course about advantages of using Seam.