Jboss Seam: Simplicity and Power Beyond Java Ee

by Michael Juntao Yuan and Thomas Heute

A new edition of this title is available, ISBN-10: 0137129394 ISBN-13: 9780137129393 Discover JBoss Seam: the Unified Framework for Simpler, More Powerful Web Development JBoss Seam integrates EJB 3.0... This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 0131347969
• ISBN13: 9780131347960
• Release Date: April 2007
• Publisher: Prentice Hall
• Length: 402 Pages
• Weight: 1.85 lbs.
• Dimensions: 1.0" x 7.1" x 9.2"

Customer Reviews

Is the future!

For that ones who like to be on cut of the edge, should read it. Easy to understand and read. Seam is leaving the future choice to be one real and excellent choice for present integrating JSF and EJB 3.x and this book has filled all that I could expect about learn JBoss Seam.

Excellent book on seam

Its a great book.. It difficult to learn Seam without this book. It may be slightly dated, with Seam 2.0 coming out recently. But per the author, there are not significant changes in the code ie mainly config changes. (eg they recommend JPA with tomcat instead of embedded server option with tomcat) Seam(and specifically seam-gen) still has some significant bugs/issues to iron out(but workaround exists).

EXCELLENT INTRODUCTION TO SEAM!

I needed to develop a project and fast. I purchased this book because I needed to get Seam up and running quickly. I found it very clearly written: with helpful examples and source code. It also provides a introduction to AJAX and has a few chapter on how to integrate AJAX with JSF and Seam. Very interesting! I recommend this book 100 percent!

concise code examples

Yuan and Heute offer the Java programmer a very tempting route away from using the standard Java Enterprise Edition. As they point out, EE version 5 is an uncomfortable mixture of EJBs and JSF. The EJBs exist on the server side and encapsulate business logic. While the JSF is used, also on the server side, as a model-view-controller framework for Web work. In general, separating the MVC from the business logic is correct. But if you have to code EJBs and JSF together, then things get awkward. Code gets verbose and hard to structure. The book's alternative is Seam, which is meant to be a filler between EJBs and JSF. One nice aspect is that Seam is inherently stateful. For a Web user session, this is vital, and it's nice from the text to see state built into Seam, without you having to shoehorn it in. Perhaps the most persuasive parts of the book are the code examples. Granted, the authors wrote these to be as concise and elegant as possible. But if you accept that most authors of computer books do this, then you can quickly appreciate the contrast between the code here and comparable code in texts on EJBs and JSF. The latter code examples are much longer and more intricate. The brevity of code writing that Seam affords you can greatly help in two ways. Quicker to write. And quicker to debug. Having said this, I am undecided about one aspect of the text. Involving what is called "dependency bijection". It is meant as a lightweight way for POJOs to interact with each other. As opposed to using framework interfaces or abstract classes. But the extensive use of interfaces (and abstract classes) has led to the successful development of extensible packages like Eclipse. (And I'm sure readers can cite other examples.) Is it the case that interface implementations do have limitations, perhaps in the context of Web servers and business logic?