InfoQ reports that JBoss Seam 1.0 was released today: JBoss SEAM 1.0: rethinking web application architecture. The article lists some of the key features of Seam. One that surprised me was the way Seam makes EJB session beans available as Javascript objects in the browser. Web clients can also directly send and receive JMS messages through Javascript. Seems like a productive way to support AJAX.
Does make you think though. For some time oo people have been saying that business rules need to be implemented in the business layer, whereas database oriented people have insisted on implementing most of the business rules in the database. Seems to me that with Seam the EJBs are more tightly coupled to the user interface, and less reusable. To implement generic business rules you’d have to add another layer of user interface independent EJB’s. But maybe it’s better to just put the business rules near the data?
June 14th, 2006 at 00:30:57
Nope, if you try out Seam, you will realize that business logic is where it should have been for the last few years as a stateless or stateful session bean. The business logic is now a reusable business bean that can used in the web framework (JSF), exposed as a Web Service, or exposed to a Swing UI through a variety of tunnels.
I also found that the number of managed beans in my JSF web framework dwindled as they became session based services. That is a huge plus since these services are no longer tightly coupled with the UI.