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

3. Why Seam?

4. Features.

5. CRUD App demo with seam-gen.

6. Q&A

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)

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

20. It makes persistence a breeze

21. Annotations over XML, end to end

22. Automated integration testing using TestNg and JUnit

23. And many more … (Rules Engine, BPM, Ajax Support, Pdf, E-mail, RESTful …)

24. Open source. Open standards. Future of Java EE

26. No DTOs

28. Traditional contexts for Java Servlets focused on technology instead of on application

29. EJB itself has no strong model of state management

30. We need a richer context model that includes “logical” context

31. We should be able to use annotations everywhere

32. An EJB should be able to be a JSF managed bean (vice versa)

33. Main idea: realization of desktop-like wizards and dialogs, possibly in parallel

34. It makes sense to think of binding EJB components directly to the JSF view

35. The Seam Context Model *source: www.reverttoconsole.com

37. Multi-window operation

38. “ Workspace Management”

39. Stack of continuable states (nested conversation)

42. Each conversation resides in its own Browser or Tab User Session Browser1 Browser2 Browser3 User Concurrent Conversations C3 C2 C1

44. Define navigation rules for each page

45. Flow is based on events and conditions

47. CRUD operations

48. • persist();

49. • getInstance();

50. • update();

54. Sub view processing

56. Client validations

58. The JBoss Embeddable EJB3 container is a great platform for integration testing: perform an end to end testing in it’s own embeddable container -- in a single unit test!

59. Test he entire flow of a request or conversation

60. Test all layers of Java code in the application, from presentation to persistence.

62. Generate CRUD views

63. Reverse engineering of POJOs

64. Entity model validations enforced with ajax feedback

65. Generates Ant build script itself

66. Ready made project files for eclipse, netbeans, idea

67. Basic page level authorization

68. Datasource creation and configuring persistence layer

69. Richfaces Ui components

72. A unified development platform of {programming model, frameworks, best practices and tooling}

74. Richfaces 3.3 - http://www.jboss.org/jbossrichfaces/docs/

75. Richfaces book – Practical Richfaces (Max Katz)

76. JSF 2 (includes “seam” like features) - http://nejug.org/events/show/91

77. EJB 3.1 - http://jcp.org/en/jsr/detail?id=318

78. Seam Books – Seam in Action (Dan Allen) & Seam Framework – Experience the evolution of Java EE (Jacob Orshalick)

79. Tools: JBoss Tools for Eclipse. Intellij and Netbeans also have excellent support for Seam