Refactoring « Design « Java Articles

1.	Build Deploy
2.	Class
3.	Core Library
4.	Data Types
5.	Database JDBC
6.	Design
7.	Development
8.	File Input Output
9.	Graphics Desktop
10.	J2EE Enterprise
11.	J2ME Wireless
12.	JVM
13.	Language
14.	Library Product
15.	Network
16.	Security
17.	SOA Web Services
18.	Test
19.	Web Development
20.	XML

Java Articles » Design » Refactoring

1. Refactoring in Java today.java.net

2. Refactoring with Martin Fowler artima.com

Over the last decade, Martin Fowler pioneered many software development techniques in the development of business information systems. He's well known for his work on object-oriented analysis and design, software patterns, Unified Modeling Language, agile software processes (particularly extreme programming), and refactoring. He is the author of Analysis Patterns (Oct. 1996), Refactoring (June 1999; coauthored with Kent Beck, et al.), UML Distilled (Aug. 1999; with Kendall Scott), Planning Extreme Programming (Oct. 2000; with Kent Beck), and the soon to be released Patterns of Enterprise Application Architecture (Nov. 2002), all published by Addison Wesley.

3. The busy Java developer's guide to db4o: Database refactoring with db4o ibm.com

This time, I'll continue that theme -- the many options found in db4o -- with a look at how it handles refactoring. As of version 6.1, db4o automatically recognizes and handles three different kinds of refactoring: adding a field, removing a field, and adding a new interface to a class. I won't cover all three (I'll focus on adding a field and changing a class name), but I will introduce you to what's most exciting about refactoring with db4o -- which is its introduction of backward- and forward-compatibility to database change management.

4. Automation for the people: Continual refactoring ibm.com

Over the years, I've seen lots of source code from many projects, ranging from elegant designs to code that appeared to be bundled together with duct tape. I've written new code and maintained other developers' source code. I'd rather write new code, but I enjoy taking some existing code and reducing complexity in a method or extracting duplicate code into a common class. Earlier in my career, many believed that if you weren't writing new code, you weren't being productive. Fortunately, in the late 1990s, Martin Fowler's book Refactoring (see Resources) helped make the practice of improving existing code without changing external behavior ? well ? cool.

5. Refactoring for everyone ibm.com

Refactoring is changing the structure of a program without changing its functionality. Refactoring is a powerful technique, but it needs to be performed carefully. The main danger is that errors can inadvertently be introduced, especially when refactoring is done by hand. This danger leads to a common criticism of refactoring: why fix code if it isn't broken?