Beginning HTML with CSS and XHTML incorporates practical examples that will show you how to structure your data correctly using (X)HTML, together with styling and layout basics using CSS. It also shows how to add dynamic behavior to your data using the JavaScript. language. All of the featured code and techniques are standards compliant and demonstrate best practices.so you will not waste time on any outdated techniques.

Errata Submission

If you think that you've found an error in Practical JBoss® Seam Projects, please let us know about it. You will find any confirmed erratum below, so you can check if your concern has already been addressed.

Errata

Issue	Author's Response
Chapter 1 page 7. Naming mEntityManager is annoying and does not conform to standard Java naming convention. Should be entityManager.	This is not an errata. Personal taste in variable names is impossible to resolve for all readers.
Chapter 1 page 8 The exceptions thrown by the persist method are all instances of RuntimeException. Therefore, the try/catch around mEntityManager.persist is useless, and, even worse, it swallows the exception.	Not an errata.
Chapter 1 page 8 try / catch with e.printStackTrace() Poor programming (swallowing exception). Should be: throw new RuntimeExpection(e)	Thank you for the coding advice. This is not an error and this technical detail is not salient to the point being made, so this will be a low priority change to be made in a future version of the book.
Chapter 1 page 6 "TYPE" is a reserved word in DB2.	Changing the column name will introduce lots of changes later in the chapter and the book. Recommended short-term solution is to expand on the Practical Tip on page 7 where this is discussed, and add language about TYPE being reserved in DB2, so we'd have to adjust the schema if we were using that database.
Chapter 4 Page 70-71 In the lower half of page 71 there is a three-item list describing key stages in the JSF lifecycle. The paragraph before the list links the list elements to stages highlighted in figure 4-3 (page 70). However, in figure 4-3 the highlighted stages are 1, 6 and 7 but the described stages are 1, 2 and 7.	Figure 4-3 should be adjusted so that the phase transitions labeled 1, 2 and 7 are highlighted in bold, instead of 1, 6 and 7 as it is now.
Chapter 8 Page 212 Listing 8-2 In the mentioned listing the function searchGadgetsCallback refers inside the if-block to the undefined variable "searchField". Shouldn't that be "inputElement"?	No, the code listing is correct. The second argument to the search() method in the mapped Javascript is a callback method to invoke. The searchGadgetsCallback() function is defined immediately after the searchGadgets() function in question.
Chapter 7 Page 191 Summary The penultimate sentence "You saw some how these persistence needs impacted..." sounds odd. I guess it should read "You saw how some of these persistence needs impacted..."	Sentence should be revised to read: You saw how some of these persistence needs impacted our use of business processes in the Gadget Catalog.
Chapter 7 Page 184 The listing snippet (see the line in bold) in the first paragraph is not in sync with the larger listing 7-2 on page 176. The larger listing reads <assignment actor-id="#{gadget.submitter.idStr}"/>, which seems to be correct. The snippet on page 184, however, reads <assignment actor-id="#{submitterID}"/>. Further, the transition should be to "review-fork" instead of "review-core" in both listings.	Correct - the code snippet on page 184 should be adjusted, with the bolded line replaced with: <assignment actor-id="#{gadget.submitter.idStr}"/>
Chapter 7 Page 176 Listing 7-2 According to figure 7-6 on page 175 the "reject" transition of task-node "verify-revisions" should point to "review-fork" instead of "review-core", which also appears to be the more logical choice.	Correct, Listing 7-2 should be revised as described.
Chapter 7 Page 166 Figure 7-2 In the above mentioned figure the conversation attached to the "Revise article" task is named "Tech edit". I assume it should also be named "Revise article"	Yes, the figure should be revised and the Conversation linked to the "Revise article" task should be named "Revise article"
Chapter 5 Page 106 In "Seam's Pageflow Model" it is referred to figure 5-1. It is stated that the start page has a transition "save" which action is linked to the addUser() method. However, in figure 5-1 the method is called "saveUser".	Yes, this is an error in the text. In the last sentence of the first paragraph on page 106, "addUser()" should be replaced with "saveUser()".
Chapter 4, Page 92. I believe the second code example is missing the id= parameter in the annotation.	Yes, the id attribute was lost in production somewhere. The first line of the code example should be: @Begin(nested=true, id="edit-gadget-#{gadget.id}")