Java Reference
In-Depth Information
Table A.1
Cross-reference of antipatterns by name
(continued)
Name
Description
Solution
Symptoms
Location
7. Everything Is
an EJB
This is the generic form of the
Round Bean in a Square Hole anti-
pattern. If a problem is not well
suited, an EJB solution is likely to
be too difficult or will perform
poorly.
Use alterna-
tives to EJBs
Poor performance,
high expense for
simple solutions
Chapter 8,
Section 8.5
8. Excessive
Layering
Object-oriented systems are easy
to layer with excessive complexity
that is not required to adequately
describe the relationships and
behavior in the model. The com-
plexity of the software can easily
outpace the capabilities of the
hardware platform.
Refactor; inte-
grate early and
often
Poor performance,
poor readability
Chapter 2
Section 2.3.4
9. Fat
Commands
Functionality that belongs in the
model or controller can creep into
the command layer.
Refactor into
model-based
commands.
Command layers
change with every
change in model.
The command
layer looks like a
utility collection.
Chapter 4,
Section 4.5
10. Hardwired
Connections
For business-to-business connec-
tions, a common implementation
is to enumerate all of the fields in
an entire interface, complete with
parameter and return types. The
connection is then made through
some form of a remote procedure
call. This approach makes the con-
nection difficult to maintain and
support as the interfaces change.
XML messages
or web services
Multiple versions
of the same inter-
face; interface
support lagging
the capabilities of
both the client
and server sys-
tems.
Chapter 7,
Section 7.4
11. Incomplete
Process
Transitions
Many fail to get the full benefits
from object-oriented technologies
and iterative processes because
they fail to make a full transition to
the new development process.
Education, lead-
ership
Long cycles, anal-
ysis paralysis,
overruns
Chapter 2,
Section 2.5.2
