This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
<pre> Author/s : Matjaz B Juric, S Jeelani Basha, Rick Lander, Ramesh Nagappan Publisher : Wrox Category :J2EE & Distributed Computing Review by : Frank Carver Rating : 7 horseshoes</pre> This book is one of those huge co-authored Wrox books on a broad area In this case the topic is Enterprise Application Integration (EAI) - getting old and/or incompatible "legacy" systems to work together. As with many such books, the content varies in quality, detail and usefulness. EAI is a tough area, and the overview and strategy sections are very good. From any other publisher they would be a separate book. The section on EAI process is almost as good, but it just presents a process with no discussion of shortcomings or alternatives. The rest of the book is taken up with technical sections, mostly about the various J2EE APIs which can help an EAI project. It's in this area that the book is weakest. Some of the material is effectively redundant (the EJB, Servlet and JSP APIs are covered much better in many other books, for example) or lacks detail (the key area of client emulation and "screen scraping" gets lots of mentions but nothing about how to do it, etc.). In general this section of the book tends to gloss over the "hard stuff". I was disappointed to find no bibliography or references for further reading. A book like this is just an introduction to the topic. You'll need to look elsewhere to actually make things work. Despite the negative points, this is still a valiant attempt to cover a large, and often overlooked, area. If you are integrating legacy systems it's well worth the price. More info at Amazon.com More info at Amazon.co.uk
The aim of this book is to help you integrate all sorts of legacy aplications, from spreadsheets to mainframes. You have to access these legacy system using whatever interfaces they provide, things like messaging, screen-scraping, DCE, CORBA, COM, SQL, etc. etc. Once you have a way of getting information in and out of the legacy systems, then you have to gather them together in an efficient, effective and extendable way to provide new, integrated, services. This is where J2EE comes in. A messaging system on its own can only solve part of the EAI puzzle.