Effective Java, Second Edition by Joshua Bloch is an updated version of the classic first edition, which was the winner of a 2001 Jolt Award. This edition has been updated to discuss Java 6 language features including generics, enums, annotations, autoboxing, the for-each loop, varargs, and concurrency utilities. InfoQ asked Bloch several questions about the areas that the new edition covers.
A misconception lingers in the Ruby world: Ruby has no debugger. This is blatantly wrong - Ruby has debuggers, GUIs for debuggers and APIs for debuggers. InfoQ takes a close look at the state of debugging tools in the Ruby world - and finds that its debugging support is more than sufficient.
Patrick Smacchia is a Visual C# MVP with over 15 years of software development experience. He is the author of Practical .NET 2 and C# 2, books about the .NET platform. He has worked on software in a variety of fields including the stock exchange at Société Générale and a satellite base station at Alcatel. He's currently the lead developer of the tool NDepend.
Annotating existing object graphs - we show a simple, extensible solution using Ruby's singleton classes.
Srini & Kavitha Penchikala give an overview of the support provided by Spring framework in the areas of unit and integration testing, with a sample application. 16
Mark Figley talks about enforcing coding standards and best practices in an automated fashion through the build process. 5
In this InfoQ article, Boris Lublinsky highlights the problems with exception handling in SOA, and suggests applying SOA principles to exception handling as a solution. 7
A comprehensive intro to the MOle, a plugin that provides insight into the inner workings of Ruby on Rails in realtime, as requests come in and get processed. 3
SOA and Agile: Which is right? Which is better? Are we comparing apples and oranges? Can they be used together, and if so, how? This is a discussion topic so come and put in your 2 cents! 22
Tess Ferrnandez, an escalation engineer in PSS (product support services) at Microsoft, outlines the procedure for tracking down where in your code an exception occurred by using a stack dump.