Developer's Guide errata

This file provides a summary of corrections and updates made since the product was packaged for final release. These changes apply to the print (and, in most cases, the online) version of the book. The page numbers correspond to the print manual, and may not match the page numbers in the PDF version. In the HTML and PDF versions, you can search to find the appropriate section.

• Global fixes: In multiple chapters, the convention for referring to the Enhydra root directory, <enhydra_root>, is not used consistently. This short-hand method for referring to directories handles variations in installations and reduces repetitious directory listings by replacing the path for your Enhydra installation, starting at the root. For example, the convention is used to refer to the directory /usr/local/lutris-enhydra3.5/dods/ as <enhydra_root>/dods/.

  In several places, preceding directories are unnecessarily included. For example, /usr/local/<enhydra_root>/apps/ should be <enhydra_root>/apps/.

• On page 53 of Chapter 4, in the section titled "Using mapping tables for generated class names," we describe how to create mappings with the XMLC Compiler wizard. The text, however, does not reflect the information in the associated dialog box illustrated in Figure 4.3. The text that reads:

  The dialog box in Figure 4.3 shows how to set up the compiler to use the org.enhydra.kelp.sample.presentation package name when compiling HTML pages stored in /usr/local/jbuilder/kelp2/sample/org/enhydra/kelp/sample/resources.

  Should read:

  The dialog box in Figure 4.3 shows how to set up the compiler to use the kelp.webapp.presentation package when compiling HTML pages stored in D:/jbuilder4/kelp2/samples/webapp/src/kelp/webapp/resources.

• On page 60 of Chapter 4, in the section titled "XMLC project property page," we describe, among other things, how to define a mapping table to map source files for a given directory to a specific package. The example cited in the text is inaccurate. The sentence that reads:

  For example, the Kelp sample project uses a mapping table to map all the HTML files in a resources directory into the org.enhydra.kelp.sample.presentation package.

  Should read:

  For example, the sample Kelp Web application project uses a mapping table to map all the HTML files in a resources directory into the kelp.webapp.presentation package.

• On page 66 of Chapter 4, in the section titled "The sample servlets," we describe the servlets that are included in the sample Kelp Web application. The package that contains these presentation objects is cited incorrectly. The sentence that reads:

  The Java files are located in the org.enhydra.kelp.webapp.presentation package.

  Should read:

  The Java files are located in the kelp.webapp.presentation package.

• On page 67 of Chapter 4, in the section titled "Debugging Enhydra applications," we provide instructions to illustrate how to debug an Enhydra application from within an IDE. The instructions use TableServlet.java from the sample Kelp Web application, but the method referenced in the instructions is no longer used. The step that reads:

  Locate the for loop of the fixupTable() method and click the left edge of the editor to put a breakpoint on the line that reads table.appendChild(newRow);

  Should read:

  Locate the for loop of the clearTable() method and click the left edge of the editor to put a breakpoint on the line that reads table.appendChild(newRow);

• On page 68 of Chapter 4, in the section titled "Working with the Kelp source code," we provide information about downloading and building the Kelp source code. The information in this section is superceded by information in the updated Lutris Enhydra installation instructions. The Kelp source is included in the Lutris Enhydra source download. Optionally, the Kelp module can be built when the Lutris Enhydra source is built. The README in the root directory for the Lutris Enhydra source also contains instructions and requirements for building Lutris Enhydra and Kelp from the Lutris Enhydra source.

• On page 147 of Chapter 9, in the section titled "Solaris," we list the system requirements for running Enhydra Director on a Sun Solaris system. The requirement that reads:

  Sun Solaris version 2.6 running on a Sparc-compatible system with 64 MB RAM (128 MB recommended)

  Should read:

  Sun Solaris version 2.6 or higher running on a Sparc-compatible system with 64 MB RAM (128 MB recommended)

• On page 208 of the Index, there are two primary level index entries for Data Object Design Studio. The first entry provides several secondary level entries with page numbers for pertinent topics. The second entry references the DODS index entry on page 210. However, since the DODS entry merely refers back to Data Object Design Studio, the second Data Object Design Studio entry is unnecessary and potentially confusing. Please disregard the second entry.

Copyright © 2000, 2001 by Lutris Technologies Inc. All rights reserved.
The Lutris and Enhydra logos, Enhydra XMLC, Enhydra Enterprise, and InstantDB are trademarks or registered trademarks of Lutris Technologies, Inc. All other trademarks, trade names or company names referenced herein are used for identification only and are the property of their respective owners.