12311Harness the power of log4j with Jabberhttp://www-106.ibm.com/developerworks/java/library/j-instlog/?ca=dgr-jw766j-instlogNo matter how many well-designed test cases you write, even the smallest application will hide one or more bugs once it's deployed in the production environment. While test-driven development and QA practices improve code quality and provide confidence in the application, when a system fails, developers and system administrators need contextual information about its execution. With the appropriate information, they can identify the nature of the problem and fix it quickly, saving time and moneyJava > Tips and Tutorials > MiscellaneousOct 12, 2006
Here is a short article that may help you while creating a struts project in Eclipse's latest 3.30 i.e Ganymede (I wonder what they will do when all the satellites' names are used
This chapter provides tutorial notes on 'javap', the Java class file disassember. Topics include list of 'javap' command options, showing public variables and methods, showing private variables and methods, disassembling bytecode to JVM assembler code.
Structural Analysis for JavaTM (SA4J) is a technology that analyzes structural dependencies of Java applications in order to measure their stability. It detects structural "anti-patterns" (suspicious design elements) and provides dependency web browsing for detailed exploration of anti-patterns in the dependency web. SA4J also enables "what if" analysis in order to assess the impact of change on the functionality of the application; and it offers guidelines for package re-factoring.
There are a number of different code reviews you can use to enhance the quality of your Java projects. The the primary difference between them is their level of formality. The different code reviews are broken down into three categories, and these are code walkthroughs, code inspection, and code reading. A code walkthrough is the most basic of the three. A code walkthrough occurs when programmers get together to study the codes they've created. A code inspection is the most challenging of the three. It is was first developed in the 1970s, and it follows a process in which each programmer has a specific role
If you're looking for a unique programming challenge, try your hand at building a management application for a distributed, cross-platform network. Consider, for example, what it takes to build a storage network. Network switch and hub technology is typically purchased from one vendor, storage appliances from another vendor, and file servers and software from yet another set of vendors. And then it's up to you to make sure they all work together, with nary a hiccup. Luckily, two technologies have the potential to vastly improve the current state of affairs. This article is the first in a three-part series that looks at how Sun Microsystems's Jiro technology and the Distributed Management Task Force's Web-Based Enterprise Management Initiative (WBEM) can simplify the creation of management applications for heterogeneous environments. Author Paul Monday launches the series this week with a beginner's introduction to the Federated Management Architecture and Jiro technology.
Joining mailing list will entitle you
to receive occasional emails informing you of news and
updates to the site and any special offers that may be
of interest to you.