JBoss Seam : Stitching JSF and EJB3
|tedious code often found in the JEE and JSF coding.
Figure 3: JSF and JSP
As the number of UI elements increases, the amount of the code performing the tedious task
also increases. Much of the tedious code is generated as a result of the deficiency lying with the inefficient combination of the JEE and JSF. Such deficiencies are concerned with the issues like the UI components are not directly usable as application objects, similarly the application objects are not enough capable to persist information.
Additionally, JSF applications can not completely escape from the stateless nature of
the HTTP protocol. Still it needs the alternative mechanisms, such as cookies or HTTP sessions to maintain the application state between more than one web page. This adds as a major
contributor leading to the JEE code-bloat.
Lets Explore the role of JBoss Seam in reducing the coding surface
Figure 4 shows how JBoss Seam reduces the potential coding surface. Apart from the component layout code, Seam enables the developers just to code the needed business logic.
Figure 4: How JBoss Seam fights code-bloat
Seam achieves the code reduction via employing
the modern framework techniques like to automate the code generation process( based on compile time inspection of the application objects), to intercept dynamically and to provide the behavioral modification at runtime. Much of what JBoss Seam does is completely invisible to the application developers however still it requires the developers to know a lot about the JEE 5 runtime environment and JSF in particular.
Systematic code reduction with Seam
JBoss Seam has eliminated a lot of coding part that developers need to support previously. Seam exactly identified the earlier deficiencies lying with the JEE and JSF combination. Now seam has reduced the task of developers, they no longer have to create the JSF backing beans and write code to coordinate the transferring data between JSF components and the backing beans. Seam generates the JSF backing beans and coordinates the data shuttling between these beans and the application object. Even the developers no longer need to write the object persistence code for their application objects as Seam itself generates and manages them. Moreover, Seam developers can even :
Nov 2007 | Java Jazz Up | 18
|View All Topics
|All Pages of this Issue
69 Download PDF