Errata

Java Database Best Practices

Errata for Java Database Best Practices

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page 11-4
Example 11-4. Using a properties file to achieve portability

...

try {
ResourceBundle bdl = ResourceBundle.getBundle("connect");
...
Enumeration keys = bdl.keys( );

should be : Enumeration keys = bdl.getKeys( );

}
Class.forName(bld.getString("driver")).newInstance( );
should be : Class.forName(bdl.getString("driver")).newInstance( );
(bdl)
...
catch( SQLException e ) {
e.printStackTrace( );
}

I have to add the following to make it work, but I am not sure that it is necessary:

catch( java.lang.ClassNotFoundException cnfe)
{
cnfe.printStackTrace( );
}

catch( java.lang.InstantiationException ie )
{
ie.printStackTrace();
}

catch( java.lang.IllegalAccessException iae )
{
iae.printStackTrace();
}

...

Anonymous   
Printed Page 41
figure 2-7

the link-table for FilmReviewer should be Reviewer, not GenreFilm (as in figure 2-8, page 42)

Anonymous   
Printed Page 50
figure 2-11

Figure 2-11 does not seem to fit at all with the text describing it.
First of all, it is not a class diagram (at least not with the conventional UML
notation). Then adresses and phone numbers are mentioned in the text (and also later
on page 52 in the "Multivalued Attributes" section) but do not appear anywhere in the
diagram.

Anonymous