Java Ee6 Cookbook for Securing, Tuning, and Extending Enterprise Applications

Java Ee6 Cookbook for Securing, Tuning, and Extending Enterprise Applications

by Mick Knutson

Paperback

$39.99
View All Available Formats & Editions
Choose Expedited Shipping at checkout for guaranteed delivery by Thursday, August 22

Product Details

ISBN-13: 9781849683166
Publisher: Packt Publishing
Publication date: 06/25/2012
Pages: 356
Product dimensions: 7.50(w) x 9.25(h) x 0.74(d)

Customer Reviews

Most Helpful Customer Reviews

See All Customer Reviews

Java Ee6 Cookbook for Securing, Tuning, and Extending Enterprise Applications 4 out of 5 based on 0 ratings. 1 reviews.
Boudville More than 1 year ago
Oracle, the owner of Java, continues to actively improve it. Despite initial fears by some when it purchased Sun, the originator and previous owner of Java. This timely book explains the enterprise version of Java 6. There is nothing here about changes to the syntax of the core language. That is Java 6 standard edition. Instead the book delves into a formidable list of packages and specifications that describe vital parts of java suitable for (primarily) web services. One new feature is the explicit hailing of APIs that are scheduled for deletion. Well, actually Oracle has taken a very conservative approach. Any labelled as such might [and note - 'might'] be deleted in java ee 7. The idea is to give you developers plenty of advance notice. So that, for example, you might want to start redesigning your architecture now. Or ponder carefully if you really want to continue writing code that uses those APIs. Like what APIs? Take JAV-RPC 1.1 for instance. In part the text explains that the moniker RPC was misleading. It is not all remote procedure calls, as the name might suggest. Instead, Oracle has shifted this to increasingly use web services. A far more loosely coupled approach. Then take our 'friends' the Entity Beans. These are being dumped! So EJBs are now only Session Beans. Many programmers who have struggled with entity beans since 1998 will be pleased. They were often kludgy and implementations were routinely slow. Some of you, while celebrating the news, might wonder why it took Sun/Oracle so long to respond to numerous complaints. While only the first chapter of the book talks about the above, you may want to very carefully go over this. While comparing to any legacy code you might have that impinges. Perhaps after you have dealt with this issue, you can proceed rhto the rest of the text.