From line 2 changed to line 2:
Seam makes the task of defining and accessing stateful business-logic components simple. Regardless of whether you have an EJB or non-EJB component, a simple @Name annotation atop a class gains it admission into Seam's contextual container. The container wraps these components in method interceptors, enabling enterprise services, such as transactions, security, and component assembly, to be declared with equivalent ease by applying annotations at the class, method, or field level. Seam grants the technologies that it integrates access to the components in this container, primarily through the use of the unified EL. This arrangement facilitates the use of JPA entity classes as "backing" beans for JSF forms, EJB session beans or transactional JavaBeans as action listeners on JSF UI components, and by resolving variables on demand using Seam's factory or manager mechanism.
Seam makes the task of defining and accessing stateful business-logic components simple. Regardless of whether you have an EJB or non-EJB component, a simple @Name annotation atop a class gains it admission into Seam's contextual container. The container wraps these components in method interceptors, enabling enterprise services, such as transactions, security, and component assembly, to be declared with equivalent ease by applying annotations at the class, method, or field level. Seam grants the technologies that it integrates access to the components in this container, primarily through the use of the unified EL. This arrangement facilitates the use of JPA betting <a href="http://pariuri365.webs.com" style="color: #000;">pariu365</a> entity classes as "backing" beans for JSF forms, EJB session beans or transactional JavaBeans as action listeners on JSF UI components, and by resolving variables on demand using Seam's factory or manager mechanism.
From line 4 changed to line 4:
-- excerpts taken from Seam in Action, Manning 2008
-- excerpts borrowed by author from Seam in Action, Manning 2008