From a practical perspective, many widely-used frameworks require application programmers to use JavaBeans (or something similar) to model database records. This is deeply unfortunate, because it doesn't allow programmers to take advantage of the many positive qualities of immutable objects.
John O'Hanley, Javaworld.com, 29 July 2008
In web page design, and generally for all markup languages such as SGML, HTML, and XML, a well-formed element is one that is either:
* opened and subsequently closed,
* an empty element, which in that case must be terminated,
* properly nested so that it does not overlap.
For example, in HTML: <b>word</b> is a well-formed element, while <i><b>word</i> is not, since the bold element is not closed. In XHTML, empty elements (elements that inherently have no content) should be closed by putting a slash at the end of the opening tag, e.g. <img />, <br />, <hr />, etc. In HTML, there is no closing tag for such elements, and no slash is added to the opening tag.
Furthermore, if an element has any attributes, each attribute value must be properly quoted.
In a well-formed document,
* all elements are well-formed, and
* a single element, known as the root element, contains all of the other elements in the document.
One thing I am a little worried about: with any book of this nature I can virtually guarantee that anyone who reads it will absolutely love some of the chapters and absolutely hate others. We certainly saw that in the review stages with early drafts of the manuscript. However, we also saw that the reviewers couldn't agree on which chapters they loved and which they hated. In fact, a chapter that one reviewer hated was usually another reviewer's favorite and vice versa.
In general I suspect the key audience for this will be IT departments inside large organisations tasked with refreshing or extending an intranet.
... the SPring Framework supports several alternative persistence layers...iBatis is generally better suited than Hibernate for the following situations:
You need to integrate with an existing database Your DBAs and application developers tend to work separately You have more junior Java developers Your data model is relatively simple