Seam is a Java web application framework that aims to provide a complete solution for developing web applications. It combines technologies like JavaServer Faces (JSF), Enterprise JavaBeans (EJB3) and Java Persistence API (JPA) to allow building stateful web applications in a simpler way. Seam eliminates unnecessary layers and provides features like conversations for state management, dependency injection, an app generator (seam-gen), and integration testing support. Seam exposes business services directly to the view layer to simplify development without separate data transfer objects or access layers.

1. Introduction to Seam Applications Nuwan Gunarathna www.geveo.com

2. Agenda Common WebApp Development Patterns.

3. Why Seam?

4. Features.

5. CRUD App demo with seam-gen.

6. Q&A

7. Today’s Web Applications Too many layers Too many Integration Points

8. Too much Xml configuration For new features, You have to lean new Frameworks

9. “ Stateless” Architecture

10. JSF falls short – Not fully enough for Web 2.0

11. Not a platform, merely a set of libraries and wrappers

12. Documentation is not at one place(Too many dependent frameworks)

13. Why Seam? To provide a Complete solution for Java Web Application Whithin an Application Is it good? Yes. Gavin King

14. Some Good Reasons Stateful Wep Applications All components are inherently stateful – no need state management Code Configuration by Exception( convention over configuration ) Idea is to have a common-sense default behaviors for components Gluing JSF and EJB3 across framework boundaries. Collapse artificial façade object layer in between Annotation based integration

15. Gives correct wayt to use ORM Lazy loading just works fine: Eliminate most encountered Exception with stateless frameworks all the time

16. Only framework that support lazy loading correctly in web application

17. Some Good Reasons cont.. No more DTOs to write

18. POJO as business services No framework interfaces, No Abstract classes