Java Reference
In-Depth Information
between classes, log it. When doing some transformation on
an object, log it. When in doubt, log it.
Once you've made the decision to log, choose an appropriate
framework. There are lots of good choices out there but we
are partial to the JDK 1.4 trace APIs, as they are fully
integrated
into
the
WebSphere
Application
Server
trace
subsystem and are standards-based.
Persistent Tier
Favor Conventions over Exceptions
In an ideal world, the default configuration settings would
always be exactly what we wanted. Our use of configuration
by exception would not require any exceptions to be
configured. We can approach this ideal world by minimizing
the frequency and severity of our deviations from the
assumed configuration. Although there is nothing inherently
wrong about providing specific exceptions to the default
configuration settings, doing so requires more effort on our
part
to
denote
and
maintain
the
metadata
describing
the
exceptions to the default configuration.
Use Portable Inheritance Mapping Strategies
Even if your JPA provider does implement the optional “table
per concrete class” inheritance mapping strategy, it is best to
avoid this if you need JPA provider portability.
It is also best to use a single inheritance mapping strategy
within a given Java entity class hierarchy, because support for
