What are some of the major attractions of Seam that make it stand out from other application frameworks?
David: So, Seam has a lot in it. The thing that I think differentiates it the most is that it doesn’t force upon the developer a single methodology or way of doing things. When you look at some of the other more popular Web frameworks out there, they all either have verbose XML that you have to configure which can be tedious and error prone. You have to extend certain classes or implement certain interfaces. And Seam is very different because it is more of an enabler than an enforcer. Simply by using annotations, you can actually mark a plain old Java object or a Stateful or Stateless Session bean or messenger bean as a Seam component and then you can use that component using a simple expression language across different areas of your application. People might think, “Well, you’re still using a proprietary API.” Well, the truth is that it is actually the foundation for the WebBeans specification. So Java WebBeans is a new JSR that is out there. So similar to the stories we’ve had befor
