db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From scotsmat...@apache.org
Subject svn commit: r547456 - /db/derby/docs/trunk/src/getstart/
Date Fri, 15 Jun 2007 00:04:28 GMT
Author: scotsmatrix
Date: Thu Jun 14 17:04:26 2007
New Revision: 547456

URL: http://svn.apache.org/viewvc?view=rev&rev=547456
Log:
Derby-2390: Updated Getting Started Guide for 10.3. Patch submitted by me.

Modified:
    db/derby/docs/trunk/src/getstart/cgsinstallingderby.dita
    db/derby/docs/trunk/src/getstart/cgsintsr.dita
    db/derby/docs/trunk/src/getstart/getstartderby.ditamap
    db/derby/docs/trunk/src/getstart/rgsdocs17307.dita
    db/derby/docs/trunk/src/getstart/rwwdactivity3.dita
    db/derby/docs/trunk/src/getstart/tgsrunningdblook.dita
    db/derby/docs/trunk/src/getstart/tgsrunningij.dita
    db/derby/docs/trunk/src/getstart/tgsrunningsysinfo.dita
    db/derby/docs/trunk/src/getstart/tgsruntoolsutils.dita
    db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita
    db/derby/docs/trunk/src/getstart/tgssetupverify.dita
    db/derby/docs/trunk/src/getstart/twwdactivity3_Setup.dita

Modified: db/derby/docs/trunk/src/getstart/cgsinstallingderby.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/cgsinstallingderby.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/cgsinstallingderby.dita (original)
+++ db/derby/docs/trunk/src/getstart/cgsinstallingderby.dita Thu Jun 14 17:04:26 2007
@@ -34,11 +34,12 @@
 and for previous official releases.</p>
 <p>The distributions are: <ul>
 <li>The <i>bin</i> distribution contains scripts, demonstration programs,
-and documentation. The optimized jar files are available in the <i>lib</i> distribution.
</li>
+documentation, and the optimized .jar files. These .ar files are the same
+set of .ar files that are in the <i>lib</i> distribution. </li>
 <li>The <i>lib</i> distribution contains an optimized, small footprint
set
-of the Derby jar files for deployment. </li>
+of the Derby .jar files for deployment. </li>
 <li>The <i>lib-debug</i> distribution contains a larger footprint set of
the
-Derby jar files that are useful for debugging or reporting issues.</li>
+Derby .jar files that are useful for debugging or reporting issues.</li>
 <li>The <i>src</i> distribution contains the source files that are used
to
 create the <i>bin</i>, <i>lib</i>, and <i>lib-debug</i>
distributions.</li>
 </ul></p>
@@ -53,25 +54,22 @@
 where you can find  information on how to use the Subversion version control
 system to access the <ph conref="../conrefs.dita#prod/productshortname"></ph>
source
 code for a specific branch or for the development trunk.</p>
-<p>Download the zip or tar archive for the distribution that you want to use.</p>
+<p>Download the ZIP or TAR archive for the distribution that you want to use.</p>
 <p>Extract the downloaded package. The extracted installation contains several
 subdirectories:<ul>
-<li>The <filepath>demo</filepath> subdirectory contains the demonstration
-programs.</li>
-<li>The <filepath>bin</filepath> subdirectory contains the scripts for
executing
-utilities and setting up the environment.</li>
-<li>The <filepath>javadoc</filepath> subdirectory contains the <codeph>api</codeph>
documentation
+<li>The <i>demo</i> subdirectory contains the demonstration programs.</li>
+<li>The <i>bin</i> subdirectory contains the scripts for executing utilities
+and setting up the environment.</li>
+<li>The <i>javadoc</i> subdirectory contains the <codeph>api</codeph>
documentation
 that was generated from source code comments.</li>
-<li>The <filepath>docs</filepath> subdirectory contains the <ph conref="../conrefs.dita#prod/productshortname"></ph>
documentation.</li>
-<li>The <filepath>lib</filepath> subdirectory contains the <ph conref="../conrefs.dita#prod/productshortname"></ph>
jar
+<li>The <i>docs</i> subdirectory contains the <ph conref="../conrefs.dita#prod/productshortname"></ph>
documentation.</li>
+<li>The <i>lib</i> subdirectory contains the <ph conref="../conrefs.dita#prod/productshortname"></ph>
.jar
 files.</li>
-<li>The <filepath>test</filepath> subdirectory contains regression tests
for <ph
-conref="../conrefs.dita#prod/productshortname"></ph>.</li>
-<li>The <filepath>frameworks</filepath> subdirectory contains older scripts
-for executing utilities and setting up the environment. These are provided
-in this release for backward compatibility. These scripts are deprecated in
-favor of the scripts in the <filepath>bin</filepath> directory, and will be
-removed in a future release. </li>
+<li>The <i>test</i> subdirectory contains regression tests for <ph conref="../conrefs.dita#prod/productshortname"></ph>.</li>
+<li>The <i>frameworks</i> subdirectory contains older scripts for executing
+utilities and setting up the environment. These are provided in this release
+for backward compatibility. These scripts are deprecated in favor of the scripts
+in the <i>bin</i> directory, and will be removed in a future release. </li>
 </ul></p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/getstart/cgsintsr.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/cgsintsr.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/cgsintsr.dita (original)
+++ db/derby/docs/trunk/src/getstart/cgsintsr.dita Thu Jun 14 17:04:26 2007
@@ -24,8 +24,10 @@
 engine written completely in Java. The database will run in any certified
 Java Virtual Machine (JVM).</shortdesc>
 <conbody>
-<p>You must have a Java Development Kit (JDK) version 1.4 or higher installed
-on your computer. To check that the correct version of Java is installed,
-issue the <codeph>java -version</codeph> command.</p>
+<p>You must have a JAVA version 1.4 or higher installed on your computer.
+The Java Development Kit (JDK) is required to perform the activities in the <xref
+href="cgstutorialintro.dita#cgstutorialintro"></xref>. </p>
+<p>To check that the correct version of Java is installed, issue the <codeph>java
+-version</codeph> command.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/getstart/getstartderby.ditamap
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/getstartderby.ditamap?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/getstartderby.ditamap (original)
+++ db/derby/docs/trunk/src/getstart/getstartderby.ditamap Thu Jun 14 17:04:26 2007
@@ -283,18 +283,6 @@
 <relcell>
 <topicref href="rgslib27507.dita" navtitle="Scripts included with Derby">
 </topicref>
-<topicref href="rgslib56653.dita" navtitle=" Libraries not provided by Derby">
-</topicref>
-</relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="rgslib56653.dita" navtitle=" Libraries not provided by Derby">
-</topicref>
-</relcell>
-<relcell>
-<topicref href="rgslib27507.dita" navtitle="Scripts included with Derby">
-</topicref>
 </relcell>
 </relrow>
 <relrow>

Modified: db/derby/docs/trunk/src/getstart/rgsdocs17307.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/rgsdocs17307.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/rgsdocs17307.dita (original)
+++ db/derby/docs/trunk/src/getstart/rgsdocs17307.dita Thu Jun 14 17:04:26 2007
@@ -57,8 +57,9 @@
 </dlentry><dlentry>
 <dt><ph conref="../conrefs.dita#pub/citutilities"></ph></dt>
 <dd>Describes how to use the <ph conref="../conrefs.dita#prod/productshortname"></ph>
tools
-such as <codeph>ij</codeph>, more advanced utilities such as import and export,
-and the database class loader.</dd>
+such as <codeph>dblook</codeph>, <codeph>ij</codeph>, and<codeph>sysinfo</codeph>,
+and how to use the system procedures to import and export data, and how to
+store Java code in the database.</dd>
 </dlentry><dlentry>
 <dt><ph conref="../conrefs.dita#pub/citadmin"></ph></dt>
 <dd>Part One of this guide discusses configuring servers, how to program client

Modified: db/derby/docs/trunk/src/getstart/rwwdactivity3.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/rwwdactivity3.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/rwwdactivity3.dita (original)
+++ db/derby/docs/trunk/src/getstart/rwwdactivity3.dita Thu Jun 14 17:04:26 2007
@@ -78,7 +78,7 @@
 JDBC driver starts the <ph conref="../conrefs.dita#prod/productshortname"></ph>
database
 engine. The <codeph>try</codeph> and <codeph>catch</codeph> block
(the Java
 error-handling construct) catches the exceptions that may occur. A problem
-here  is usually due to an incorrect classpath setting.</p>  <codeblock>String
driver = "org.apache.derby.jdbc.EmbeddedDriver";
+here is usually due to an incorrect classpath setting.</p>  <codeblock>String
driver = "org.apache.derby.jdbc.EmbeddedDriver";
 ...
 try {
     Class.forName(driver); 
@@ -146,11 +146,15 @@
 SECTION</cite>: If an application starts the <ph conref="../conrefs.dita#prod/productshortname"></ph>
engine,
 the application should shut down all databases before exiting. The attribute <codeph>;shutdown=true</codeph>
in
 the <ph conref="../conrefs.dita#prod/productshortname"></ph> connection URL
-performs the shutdown. The shutdown process cleans up records in the  transaction
-log to ensure a faster startup the next time the database is booted.</p><p>This
-section verifies that the embedded driver is being used, then issues the shutdown
-command and catches the shutdown exception to confirm that the database shut
-down cleanly. The shutdown status is displayed before the program exits.</p> <codeblock>if
(driver.equals("org.apache.derby.jdbc.EmbeddedDriver")) {
+performs the shutdown. When the <ph conref="../conrefs.dita#prod/productshortname"></ph>
engine
+is shutdown, all booted databases will automatically shut down. The shutdown
+process cleans up records in the transaction log to ensure a faster startup
+the next time the database is booted. </p><note type="tip">You can shut down
+individual databases without shutting down the engine by including the database
+name in the connection URL.</note><p>"This section verifies that the embedded
+driver is being used, then issues the shutdown command and catches the shutdown
+exception to confirm that the <ph conref="../conrefs.dita#prod/productshortname"></ph>
engine
+shut down cleanly. The shutdown status is displayed before the program exits.</p> <codeblock>if
(driver.equals("org.apache.derby.jdbc.EmbeddedDriver")) {
    boolean gotSQLExc = false;
    try {
       DriverManager.getConnection("jdbc:derby:;shutdown=true");
@@ -164,10 +168,12 @@
    }  else  {
       System.out.println("Database shut down normally");
    }
-}</codeblock> <note type="important">The XJ015 error is the only exception
-thrown by <ph conref="../conrefs.dita#prod/productshortname"></ph> that indicates
-that an operation succeeded. All other exceptions indicate that an operation
-failed. </note></section>
+}</codeblock> <note type="important"> The XJ015 error (successful shutdown
+of the <ph conref="../conrefs.dita#prod/productshortname"></ph> engine) and
+the 08006 error (successful shutdown of a single database) are the only exceptions
+thrown by <ph conref="../conrefs.dita#prod/productshortname"></ph> that might
+indicate that an operation succeeded. All other exceptions indicate that an
+operation failed. You should check the log file to be certain.</note></section>
 <section><title>The errorPrint and SQLExceptionPrint methods</title><p><cite>DERBY
 EXCEPTION REPORTING CLASSES</cite>: The two methods at the end of the file, <codeph>errorPrint</codeph>
and <codeph>SQLExceptionPrint</codeph>,
 are generic exception-reporting methods that can be used with any JDBC program.

Modified: db/derby/docs/trunk/src/getstart/tgsrunningdblook.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgsrunningdblook.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgsrunningdblook.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgsrunningdblook.dita Thu Jun 14 17:04:26 2007
@@ -34,7 +34,7 @@
 or parts of a database, viewing a subset of the objects in a database (for
 example, those objects that pertain to specific tables and schemas), or documenting
 the schema of a database. </p><p>Choose the method that you can use to run
-the <codeph>dblook</codeph> script:</p><simpletable relcolwidth="1*
2*">
+the <codeph>dblook</codeph> script:</p><simpletable relcolwidth="1*
1* 2*">
 <sthead>
 <stentry>Method</stentry>
 <stentry>When to Use</stentry>
@@ -67,9 +67,9 @@
 language and <ph conref="../conrefs.dita#prod/productshortname"></ph>, and
 you have already set the <codeph>java.exe</codeph> file in your command execution
 PATH.</stentry>
-<stentry>You must set your CLASSPATH to include the <codeph>derbyrun.jar</codeph>
file
-and then specify the class name in the <codeph>java</codeph> command.  For
-example:<codeblock>java org.apache.derby.tools.dblook -d databaseURL [options]</codeblock></stentry>
+<stentry>You must set your CLASSPATH. Use the steps specified in <xref href="tgs26250.dita#tgs26250"></xref>.
+Then specify the class name in the <codeph>java</codeph> command.  For example:<codeblock>java
org.apache.derby.tools.dblook -d databaseURL [options]</codeblock
+></stentry>
 </strow>
 </simpletable></context>
 <postreq>See "Using dblook" in the <cite><ph conref="../conrefs.dita#pub/citutilities"></ph></cite>
for

Modified: db/derby/docs/trunk/src/getstart/tgsrunningij.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgsrunningij.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgsrunningij.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgsrunningij.dita Thu Jun 14 17:04:26 2007
@@ -31,7 +31,7 @@
 <context></context>
 <steps-unordered>
 <step><cmd>Choose the method that you can use to run the <codeph>ij</codeph>
script:</cmd>
-<info><simpletable relcolwidth="1* 2*">
+<info><simpletable relcolwidth="1* 1* 2*">
 <sthead>
 <stentry>Method</stentry>
 <stentry>When to Use</stentry>
@@ -64,9 +64,8 @@
 language and <ph conref="../conrefs.dita#prod/productshortname"></ph>, and
 you have already set the <codeph>java.exe</codeph> file in your command execution
 PATH.</stentry>
-<stentry>You must set your CLASSPATH to include the <codeph>derbyrun.jar</codeph>
file
-and then specify the class name in the <codeph>java</codeph> command.  For
-example:<codeblock>java org.apache.derby.tools.ij </codeblock></stentry>
+<stentry>You must set your CLASSPATH. Use the steps specified in <xref href="tgs26250.dita#tgs26250"></xref>.
+Then specify the class name in the <codeph>java</codeph> command.  For example:<codeblock>java
org.apache.derby.tools.ij </codeblock></stentry>
 </strow>
 </simpletable></info></step>
 <step><cmd>When you are ready to leave the <codeph>ij</codeph> tool,
type: </cmd>

Modified: db/derby/docs/trunk/src/getstart/tgsrunningsysinfo.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgsrunningsysinfo.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgsrunningsysinfo.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgsrunningsysinfo.dita Thu Jun 14 17:04:26 2007
@@ -30,7 +30,7 @@
 <taskbody>
 <context>The <codeph>sysinfo</codeph> utility prints system information
to
 a console.<p>Choose the method that you can use to run the <codeph>sysinfo</codeph>
script:</p><simpletable
-relcolwidth="1* 2* 1*">
+relcolwidth="1* 1* 2*">
 <sthead>
 <stentry>Method</stentry>
 <stentry>When to Use</stentry>
@@ -63,9 +63,8 @@
 language and <ph conref="../conrefs.dita#prod/productshortname"></ph>, and
 you have already set the <codeph>java.exe</codeph> file in your command execution
 PATH.</stentry>
-<stentry>You must set your CLASSPATH to include the <codeph>derbyrun.jar</codeph>
file
-and then specify the class name in the <codeph>java</codeph> command.  For
-example:<codeblock>java org.apache.derby.tools.sysinfo</codeblock></stentry>
+<stentry>You must set your CLASSPATH. Use the steps specified in <xref href="tgs26250.dita#tgs26250"></xref>.
+Then specify the class name in the <codeph>java</codeph> command.  For example:<codeblock>java
org.apache.derby.tools.sysinfo</codeblock></stentry>
 </strow>
 </simpletable></context>
 <postreq>See "sysinfo" in the <cite><ph conref="../conrefs.dita#pub/citutilities"></ph></cite>
for

Modified: db/derby/docs/trunk/src/getstart/tgsruntoolsutils.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgsruntoolsutils.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgsruntoolsutils.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgsruntoolsutils.dita Thu Jun 14 17:04:26 2007
@@ -31,7 +31,7 @@
 <context> <p>The method that you choose to run the tools and utilities determines
 the environment variables that you set for <ph conref="../conrefs.dita#prod/productshortname"></ph>.</p></context>
 <steps>
-<step><cmd>Choose the method that you want to use:</cmd><info><simpletable
+<step><cmd>Choose the method that you want to use: </cmd><info><simpletable
 relcolwidth="1.5* 1.5* 2*">
 <sthead>
 <stentry>Method</stentry>
@@ -39,7 +39,8 @@
 <stentry>Requirements</stentry>
 </sthead>
 <strow>
-<stentry>Run the tools using the shell scripts provided.</stentry>
+<stentry>Run the tools using the command shell scripts that are provided with <ph
+conref="../conrefs.dita#prod/productshortname"></ph>.</stentry>
 <stentry>Use this method when you want to run the tools with the least amount
 of typing and have installed the full <codeph>bin</codeph> distribution of <ph
 conref="../conrefs.dita#prod/productshortname"></ph>.</stentry>
@@ -53,8 +54,9 @@
 <strow>
 <stentry>Run the tools using the <codeph>derbyrun.jar</codeph> archive
file. </stentry>
 <stentry>Use this method when:<ul>
-<li>You have only the <codeph>derbyrun.jar</codeph> file available, and
do
-not have the full <codeph>bin</codeph> distribution of <ph conref="../conrefs.dita#prod/productshortname"></ph></li>
+<li>You have only the <ph conref="../conrefs.dita#prod/productshortname"></ph>
jar
+files available (see <xref href="rgslib46043.dita#rgslib46043"></xref>), and
+do not have the full <codeph>bin</codeph> distribution of <ph conref="../conrefs.dita#prod/productshortname"></ph></li>
 <li>You do not want to use the scripts that are provided with <ph conref="../conrefs.dita#prod/productshortname"></ph></li>
 </ul></stentry>
 <stentry><ul>
@@ -85,8 +87,8 @@
 </ul><p>For details on setting the CLASSPATH, see  <xref href="tgs26250.dita#tgs26250"></xref>.</p></stentry>
 </strow>
 </simpletable></info></step>
-<step><cmd>Based on the method that you chose to run the tools, follow the
-instructions to <xref href="tgssetupjavaenvir.dita#tgssetupjavaenvir">set
+<step><cmd>Based on the requirements of the method that you chose to run the
+tools, follow the instructions to <xref href="tgssetupjavaenvir.dita#tgssetupjavaenvir">set
 the environment variables</xref>.</cmd></step>
 </steps>
 </taskbody>

Modified: db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita Thu Jun 14 17:04:26 2007
@@ -38,12 +38,10 @@
 a method to run the Derby tools and startup utilities</xref>, you must set
 the DERBY_HOME environment variable so that you can use the command examples
 that are presented in this manual.  Adding the <ph conref="../conrefs.dita#prod/productshortname"></ph>
scripts
-directory to your command execution PATH makes the scripts are easier to use
-and enables you to use the script examples in this manual.  The CLASSPATH
-environment variable must be set if you are using <ph conref="../conrefs.dita#prod/productshortname"></ph>
in
-a Java program or executing the tools using the <codeph>java</codeph> command.<p>
If
-you decide not to set the environment variables, you will need to <xref href="cgsusingtoolsutils.dita#cgsusingtoolsutils">run
-the <ph conref="../conrefs.dita#prod/productshortname"></ph> tools</xref>
manually.</p><p>The
+directory to your command execution PATH makes the scripts easier to use and
+enables you to use the script examples in this manual.  The CLASSPATH environment
+variable must be set if you are using <ph conref="../conrefs.dita#prod/productshortname"></ph>
in
+a Java program or executing the tools using the <codeph>java</codeph> command.<p>The
 steps below show you how to set the environment variables in a command window.
 The settings are only valid for that window. If you close the command window
 or open a new command window, you must set the environment variables again.<note
@@ -69,27 +67,8 @@
 </choicetable>
 </step>
 <step><cmd>Be certain that the <codeph>java.exe</codeph> file, version
1.4.2
-or, higher is in your command execution PATH.</cmd>
-<substeps>
-<substep><cmd>Open a command window and run the <codeph>java -version</codeph>
command.</cmd>
-</substep>
-<substep><cmd>If the JAVA_HOME environment variable is not set, use the following
-command to set the environment variable.</cmd><stepxmp><simpletable relcolwidth="1*
3*">
-<sthead>
-<stentry>Operating System</stentry>
-<stentry>Command</stentry>
-</sthead>
-<strow>
-<stentry>UNIX (Korn Shell)</stentry>
-<stentry><codeph>export JAVA_HOME=/usr/j2sdk</codeph></stentry>
-</strow>
-<strow>
-<stentry>Windows</stentry>
-<stentry><codeph>set JAVA_HOME=C:\Program Files\Java\j2sdk1.4.2_14</codeph>.
</stentry>
-</strow>
-</simpletable></stepxmp></substep>
-</substeps>
-</step>
+or, higher is in your command execution PATH. Open a command window and run
+the <codeph>java -version</codeph> command.</cmd></step>
 <step><cmd>Add the <codeph><ph conref="../conrefs.dita#prod/productinstallpath"></ph>/bin</codeph>
directory
 to the PATH environment variable so that you can run the <ph conref="../conrefs.dita#prod/productshortname"></ph>
scripts
 from any directory.</cmd>

Modified: db/derby/docs/trunk/src/getstart/tgssetupverify.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgssetupverify.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/tgssetupverify.dita (original)
+++ db/derby/docs/trunk/src/getstart/tgssetupverify.dita Thu Jun 14 17:04:26 2007
@@ -36,37 +36,16 @@
 <context> <p>To check the <ph conref="../conrefs.dita#prod/productshortname"></ph>
system
 configuration:</p></context>
 <steps>
-<step><cmd>Verify that the <codeph>JAVA_HOME</codeph> environment
variable
-is set properly.</cmd>
-<substeps>
-<substep><cmd>Verify that the <codeph>JAVA_HOME</codeph> executable
is set.
-Open a command window and run the command using the syntax that is appropriate
-for your system:</cmd><stepxmp><simpletable relcolwidth="1* 3*">
-<sthead>
-<stentry>Operating system</stentry>
-<stentry>Command</stentry>
-</sthead>
-<strow>
-<stentry>UNIX</stentry>
-<stentry><codeblock>% echo $JAVA_HOME</codeblock></stentry>
-</strow>
-<strow>
-<stentry>Windows</stentry>
-<stentry><codeblock>echo %JAVA_HOME%</codeblock></stentry>
-</strow>
-</simpletable></stepxmp></substep>
-<substep><cmd>Verify that the <codeph>java.exe</codeph> file, version
1.4.2
-or, higher is in your command execution PATH by opening a command window and
-running the <codeph>java -version</codeph> command.</cmd><stepresult>The
output
-from the command looks something like this:<codeblock><systemoutput>java version
&quot;1.4.2_04&quot;  
+<step><cmd>Verify that the <codeph>java.exe</codeph> file, version
1.4.2 or,
+higher is in your command execution PATH by opening a command window and running
+the <codeph>java -version</codeph> command.</cmd><stepresult>The
output from
+the command looks something like this:<codeblock><systemoutput>java version &quot;1.4.2_04&quot;
 
 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)  
 Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)</systemoutput></codeblock>
The
 output you see might be different from what is shown here because the <codeph>java
 -version</codeph> command outputs vendor-specific information. If the command
 produces an error or the version listed is not 1.4 or higher, install a JDK
-before continuing.</stepresult></substep>
-</substeps>
-</step>
+before continuing.</stepresult></step>
 <step><cmd>Verify that the  <ph conref="../conrefs.dita#prod/productinstallpath"></ph>

 environment variable is set and points to the root directory of the  <ph conref="../conrefs.dita#prod/productshortname"></ph>&nbsp;<ph
 conref="../conrefs.dita#vers/shortversionnumber"></ph>  installation. Open

Modified: db/derby/docs/trunk/src/getstart/twwdactivity3_Setup.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/twwdactivity3_Setup.dita?view=diff&rev=547456&r1=547455&r2=547456
==============================================================================
--- db/derby/docs/trunk/src/getstart/twwdactivity3_Setup.dita (original)
+++ db/derby/docs/trunk/src/getstart/twwdactivity3_Setup.dita Thu Jun 14 17:04:26 2007
@@ -72,7 +72,7 @@
 </step>
 <step><cmd>Run the program.</cmd><info>The <xref href="rwwdactivity3.dita#rwwdactivity3"><codeph>gsEmbedded.java</codeph>
program</xref> populates
 a table with wish-list items. The program prompts you for text input (up to
-32 characters),  stores the text input in a database table, and then lists
+32 characters), stores the text input in a database table, and then lists
 the items stored in the table. The program continues to ask for wish-list
 items until the you type the command <codeph>exit</codeph> or a problem is
 encountered. Some basic information on program progress is displayed at the



Mime
View raw message