View RSS Feed

JBoss

Seam - Designed for Stateful Web Applications

Rate this Entry
by , 04-27-2012 at 06:36 PM (825 Views)
Seam is designed for stateful web applications. Web applications are inherently multi-user applications, and e-commerce applications are inherently stateful and transactional. However, most existing web application frameworks are geared toward stateless applications. You have to fiddle with the HTTP session objects to manage user states. That not only clutters your application with code un-related to the core business logic, but also brings on an array of performance issues.

In Seam, all the basic application components are inherently stateful. They are much easier to use than the HTTP session since their states are declaratively managed by Seam. There is no need to write distracting state management code in a Seam application -- just annotate the component with its scope, lifecycle methods, and other stateful properties -- and Seam takes over the rest. Seam stateful components also provide much finer control over user states than the plain HTTP session does. For instance, you can have multiple "conversations", each consisting of a sequence of web requests and business method calls, in a HTTP session.

Furthermore, database caches and transactions can be automatically tied with the application state in Seam. Seam automatically holds database updates in memory and only commits to the database at the end of a conversation. The in-memory cache greatly reduces database load in complex stateful applications.

Submit "Seam - Designed for Stateful Web Applications" to Facebook Submit "Seam - Designed for Stateful Web Applications" to Digg Submit "Seam - Designed for Stateful Web Applications" to del.icio.us Submit "Seam - Designed for Stateful Web Applications" to StumbleUpon Submit "Seam - Designed for Stateful Web Applications" to Google

Comments