db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From scotsmat...@apache.org
Subject svn commit: r524118 [3/4] - /db/derby/docs/trunk/src/devguide/
Date Fri, 30 Mar 2007 15:17:11 GMT
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp27715.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp27715.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp27715.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp27715.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
 -->
 <concept id="cdevdvlp27715" xml:lang="en-us">
 <title>Booting databases</title>
-<shortdesc>The default configuration for <ph conref="devconrefs.dita#prod/productshortname"></ph> is
+<shortdesc>The default configuration for <ph conref="../conrefs.dita#prod/productshortname"></ph> is
 to <i>boot</i> (or start) a database when an application first makes a connection
-to it. When <ph conref="devconrefs.dita#prod/productshortname"></ph> boots
+to it. When <ph conref="../conrefs.dita#prod/productshortname"></ph> boots
 a database, it checks to see if recovery needs to be run on the database,
 so in some unusual cases booting can take some time.</shortdesc>
 <prolog><metadata>
@@ -32,20 +32,20 @@
 <conbody>
 <p>You can also configure your system to automatically boot all databases
 in the system when it starts up; see <i>derby.system.bootAll</i> in the <ph
-conref="devconrefs.dita#pub/cittuning"></ph> manual. Because of the time needed
+conref="../conrefs.dita#pub/cittuning"></ph> manual. Because of the time needed
 to boot a database, the number of databases in the system directory affects
 startup performance if you use that configuration. </p>
-<p>Once a database has been booted within a <ph conref="devconrefs.dita#prod/productshortname"></ph> system,
-it remains active until the <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<p>Once a database has been booted within a <ph conref="../conrefs.dita#prod/productshortname"></ph> system,
+it remains active until the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
 has been shut down or until you shut down the database individually.</p>
-<p>When <ph conref="devconrefs.dita#prod/productshortname"></ph> boots a database,
-a message is added to the error log. The message includes the <ph conref="devconrefs.dita#prod/productshortname"></ph> version
+<p>When <ph conref="../conrefs.dita#prod/productshortname"></ph> boots a database,
+a message is added to the error log. The message includes the <ph conref="../conrefs.dita#prod/productshortname"></ph> version
 that the database was booted with, for example:</p>
-<codeblock>2006-10-04 03:54:06.196 GMT: Booting <ph conref="devconrefs.dita#prod/productshortname"></ph> version <ph
-conref="devconrefs.dita#prod/productlongname"></ph>
+<codeblock>2006-10-04 03:54:06.196 GMT: Booting <ph conref="../conrefs.dita#prod/productshortname"></ph> version <ph
+conref="../conrefs.dita#prod/productlongname"></ph>
 - 10.2.1.5 - (448900): instance c013800d-00fd-0cb0-e736-ffffd1025a25 on
 database directory sample</codeblock>
-<p>The number of databases running in a <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<p>The number of databases running in a <ph conref="../conrefs.dita#prod/productshortname"></ph> system
 is limited only by the amount of memory available in the JVM.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp30653.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp30653.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp30653.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp30653.dita Fri Mar 30 08:17:01 2007
@@ -19,8 +19,8 @@
 limitations under the License.
 -->
 <concept id="cdevdvlp30653" xml:lang="en-us">
-<title><ph conref="devconrefs.dita#prod/productshortname"></ph> database limitations</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> databases
+<title><ph conref="../conrefs.dita#prod/productshortname"></ph> database limitations</title>
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> databases
 have a few limitations.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>limitations<indexterm>Derby databases</indexterm></indexterm>
@@ -35,7 +35,7 @@
 page size causes the insert to fail.</p><p>Avoid creating indexes on long
 columns. Create indexes on small columns that provide a quick look-up to larger,
 unwieldy data in the row. You might not see performance improvements if you
-index long columns. For information about indexes, see <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>. </p></section>
+index long columns. For information about indexes, see <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite>. </p></section>
 <section><title>System shutdowns</title><p>The system shuts down if the database
 log cannot allocate more disk space.</p><p>A "LogFull" error or some sort
 of <codeph>IOException</codeph> occurs in the <filepath>derby.log</filepath> file

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp34964.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp34964.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp34964.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp34964.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevdvlp34964" xml:lang="en-us">
 <title>Connecting to databases</title>
-<shortdesc>You connect to a database using a form of the <ph conref="devconrefs.dita#prod/productshortname"></ph> connection
+<shortdesc>You connect to a database using a form of the <ph conref="../conrefs.dita#prod/productshortname"></ph> connection
 URL as an argument to the <i>DriverManager.getConnection</i> call.</shortdesc>
 <prolog></prolog>
 <conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp39409.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp39409.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp39409.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp39409.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevdvlp39409" xml:lang="en-us">
 <title>Derby embedded basics</title>
-<shortdesc>This section discusses the basics of the <ph conref="devconrefs.dita#prod/productshortname"></ph> database.</shortdesc>
+<shortdesc>This section discusses the basics of the <ph conref="../conrefs.dita#prod/productshortname"></ph> database.</shortdesc>
 <prolog></prolog>
 <conbody></conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp39943.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp39943.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp39943.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp39943.dita Fri Mar 30 08:17:01 2007
@@ -27,10 +27,10 @@
 </metadata></prolog>
 <conbody>
 <p>The <i>derby.properties</i> file is not automatically created. If you want
-to set <ph conref="devconrefs.dita#prod/productshortname"></ph> properties
+to set <ph conref="../conrefs.dita#prod/productshortname"></ph> properties
 with this file, you need to create the file yourself. The <i>derby.properties</i> file
 should be in the format created by the <codeph><i>java.util.Properties.save</i></codeph> method.
 For more information about properties and the <i>derby.properties</i> file,
-see <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>.</p>
+see <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp40170.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp40170.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp40170.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp40170.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevdvlp40170" xml:lang="en-us">
 <title>Embedded Derby JDBC driver</title>
-<shortdesc>The <ph conref="devconrefs.dita#prod/productshortname"></ph> driver
+<shortdesc>The <ph conref="../conrefs.dita#prod/productshortname"></ph> driver
 class name for the embedded environment is <i>org.apache.derby.jdbc.EmbeddedDriver</i>.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>JDBC driver (embedded)</indexterm></keywords>
@@ -32,7 +32,7 @@
 your application runs on JDK 1.6 or higher, then you do not need to
 explicitly load the EmbeddedDriver. In that environment, the driver
 loads automatically.</p>
-<p>For detailed information about loading the <ph conref="devconrefs.dita#prod/productshortname"></ph> JDBC
-driver, see "java.sql.Driver interface" in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
+<p>For detailed information about loading the <ph conref="../conrefs.dita#prod/productshortname"></ph> JDBC
+driver, see "java.sql.Driver interface" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp40350.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp40350.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp40350.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp40350.dita Fri Mar 30 08:17:01 2007
@@ -31,7 +31,7 @@
 <conbody>
 <p>The path must do one of the following:</p>
 <ul>
-<li>refer to a previously created <ph conref="devconrefs.dita#prod/productshortname"></ph> database</li>
+<li>refer to a previously created <ph conref="../conrefs.dita#prod/productshortname"></ph> database</li>
 <li>specify the <i>create=true</i> attribute</li>
 </ul>
 <p>The path separator in the connection URL is / (forward slash), as in the
@@ -43,10 +43,10 @@
 <p>If two different database name values, relative or absolute, refer to the
 same actual directory, they are considered equivalent. This means that connections
 to a database through its absolute path and its relative path are connections
-to the same database. Within <ph conref="devconrefs.dita#prod/productshortname"></ph>,
+to the same database. Within <ph conref="../conrefs.dita#prod/productshortname"></ph>,
 the name of the database is defined by the canonical path of its directory
 from <cite>java.io.File.getCanonicalPath</cite>.</p>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> automatically
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> automatically
 creates any intermediate directory that does not already exist when creating
 a new database. If it cannot create the intermediate directory, the database
 creation fails.</p>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp40653.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp40653.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp40653.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp40653.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevdvlp40653" xml:lang="en-us">
 <title>Derby JDBC driver</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> consists
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> consists
 of both the database engine and an embedded JDBC driver. Applications use
 JDBC to interact with a database. Applications running on JDK 1.5 or earlier,
 must load the driver in order to work with the database.</shortdesc>
@@ -29,14 +29,14 @@
 </keywords>
 </metadata></prolog>
 <conbody>
-<p>In an embedded environment, loading the driver also starts <ph conref="devconrefs.dita#prod/productshortname"></ph>.</p>
+<p>In an embedded environment, loading the driver also starts <ph conref="../conrefs.dita#prod/productshortname"></ph>.</p>
 <p>In a Java application, you typically load the driver with the static <i>Class.forName</i> method
 or with the <codeph><i>jdbc.drivers</i></codeph> system property. For example:</p>
 <codeblock>
 Class.forName("org.apache.derby.jdbc.EmbeddedDriver");
 </codeblock>
-<p>For detailed information about loading the <ph conref="devconrefs.dita#prod/productshortname"></ph> JDBC
-driver, see "java.sql.Driver interface" in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
+<p>For detailed information about loading the <ph conref="../conrefs.dita#prod/productshortname"></ph> JDBC
+driver, see "java.sql.Driver interface" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
 <p> If your application runs on JDK 1.6 or higher, then you do not need to
 explicitly load the EmbeddedDriver. In that environment, the driver loads
 automatically. </p>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp40724.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp40724.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp40724.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp40724.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevdvlp40724" xml:lang="en-us">
 <title>The database directory</title>
-<shortdesc>A <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<shortdesc>A <ph conref="../conrefs.dita#prod/productshortname"></ph> database
 is stored in files that live in a directory of the same name as the database.
 Database directories typically live in <i>system</i> directories.</shortdesc>
 <prolog><metadata>
@@ -44,10 +44,10 @@
 <li><i>service.properties</i> file <p>A text file with internal configuration
 information.</p></li>
 <li><i>tmp</i> directory  <p>(might not exist.) A temporary directory used
-by <ph conref="devconrefs.dita#prod/productshortname"></ph> for large sorts
+by <ph conref="../conrefs.dita#prod/productshortname"></ph> for large sorts
 and deferred updates and deletes. Sorts are used by a variety of SQL statements.
 For databases on read-only media, you might need to set a property to change
-the location of this directory. See "Creating <ph conref="devconrefs.dita#prod/productshortname"></ph> Databases
+the location of this directory. See "Creating <ph conref="../conrefs.dita#prod/productshortname"></ph> Databases
 for Read-Only Use".</p></li>
 <li><i>jar</i> directory  <p>(might not exist.) A directory in which jar files
 are stored when you use database class loading.</p></li>
@@ -55,18 +55,18 @@
 <p id="cdevdvlpaccessingareadonlydatabaseinazip">Read-only database directories
 can be archived (and compressed, if desired) into jar or zip files. For more
 information, see <xref href="cdevdeploy11201.dita#cdevdeploy11201"></xref>.</p>
-<p>The following figure shows the files and directories in the <ph conref="devconrefs.dita#prod/productshortname"></ph> database
-directories that are used by the <ph conref="devconrefs.dita#prod/productshortname"></ph> software.</p>
-<fig expanse="column" id="rdevdvlp31476"><title>An example of a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<p>The following figure shows the files and directories in the <ph conref="../conrefs.dita#prod/productshortname"></ph> database
+directories that are used by the <ph conref="../conrefs.dita#prod/productshortname"></ph> software.</p>
+<fig expanse="column" id="rdevdvlp31476"><title>An example of a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
 directory and file structure.</title>
 <image href="dbcont.gif" placement="break"><alt>This figure shows the files
 and directories that might be found in the main directory of a Derby database
 called Sales: the service.properties file, and the log, seg0, tmp, and jar
 directories.</alt></image>
 </fig>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> imposes relatively
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> imposes relatively
 few limitations on the number and size of databases and database objects.
-The following table shows some size limitations of <ph conref="devconrefs.dita#prod/productshortname"></ph> databases
+The following table shows some size limitations of <ph conref="../conrefs.dita#prod/productshortname"></ph> databases
 and database objects:</p>
 <table id="cdevdvlp85623" rowheader="firstcol"><title>Size limits for Derby
 database objects</title>
@@ -114,7 +114,7 @@
 </tbody>
 </tgroup>
 </table>
-<p>For a complete list of restrictions on <ph conref="devconrefs.dita#prod/productshortname"></ph> databases
-and database objects, see the <i><ph conref="devconrefs.dita#pub/citref"></ph></i>.</p>
+<p>For a complete list of restrictions on <ph conref="../conrefs.dita#prod/productshortname"></ph> databases
+and database objects, see the <i><ph conref="../conrefs.dita#pub/citref"></ph></i>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp42173.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp42173.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp42173.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp42173.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
 <concept id="cdevdvlp42173" xml:lang="en-us">
 <title>Creating, dropping, and backing up databases</title>
 <shortdesc>You create new databases and access existing ones by specifying
-attributes to the <ph conref="devconrefs.dita#prod/productshortname"></ph> connection
+attributes to the <ph conref="../conrefs.dita#prod/productshortname"></ph> connection
 URL.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Databases<indexterm>dropping</indexterm></indexterm>
@@ -33,11 +33,11 @@
 directory with operating system commands. The database must not be booted
 when you remove a database. You can get a list of booted databases with <i>getPropertyInfo</i>.</p>
 <p>To back up a database, you can use the online backup utility. For information
-on this utility, see the <cite><ph conref="devconrefs.dita#pub/citadmin"></ph></cite>.</p>
+on this utility, see the <cite><ph conref="../conrefs.dita#pub/citadmin"></ph></cite>.</p>
 <p>You can also use <i>roll-forward recovery</i> to recover a damaged database. <ph
-conref="devconrefs.dita#prod/productshortname"></ph> accomplishes roll-forward
+conref="../conrefs.dita#prod/productshortname"></ph> accomplishes roll-forward
 recovery by using a full backup copy of the database, archived logs, and active
 logs from the most recent time before a failure. For more information on roll-forward
-recovery see the <cite><ph conref="devconrefs.dita#pub/citadmin"></ph></cite>.</p>
+recovery see the <cite><ph conref="../conrefs.dita#pub/citadmin"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp51654.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp51654.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp51654.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp51654.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevdvlp51654" xml:lang="en-us">
 <title>Working with the database connection URL attributes</title>
-<shortdesc>You specify attributes on the <ph conref="devconrefs.dita#prod/productshortname"></ph> connection
+<shortdesc>You specify attributes on the <ph conref="../conrefs.dita#prod/productshortname"></ph> connection
 URL.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Attributes to database connection URL</indexterm><indexterm>Attributes
@@ -29,14 +29,14 @@
 <conbody>
 <p>The examples in this section use the syntax of the connection URL for use
 in an embedded environment. You can also specify these same attributes and
-values on the client connection URL if you are using <ph conref="devconrefs.dita#prod/productshortname"></ph> as
-a database server. For more information, see the <cite><ph conref="devconrefs.dita#pub/citadmin"></ph></cite>.</p>
+values on the client connection URL if you are using <ph conref="../conrefs.dita#prod/productshortname"></ph> as
+a database server. For more information, see the <cite><ph conref="../conrefs.dita#pub/citadmin"></ph></cite>.</p>
 <p>You can also set these attributes by passing a <i>Properties</i> object
 along with a connection URL to <codeph><i>DriverManager.getConnection</i></codeph> when
 obtaining a connection; see "Specifying Attributes in a Properties Object".</p>
 <p>All attributes are optional. For detailed information about the connection
-URL syntax and attributes, see "<ph conref="devconrefs.dita#prod/productshortname"></ph> Database
-Connection URL Syntax"in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
+URL syntax and attributes, see "<ph conref="../conrefs.dita#prod/productshortname"></ph> Database
+Connection URL Syntax"in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
 <p>You can specify the following attributes:</p>
 <ul>
 <li><i>bootPassword=key</i>  </li>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp84026.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp84026.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp84026.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp84026.dita Fri Mar 30 08:17:01 2007
@@ -24,6 +24,6 @@
 it.</shortdesc>
 <prolog></prolog>
 <conbody>
-<p>For more information, see the <cite><ph conref="devconrefs.dita#pub/citadmin"></ph></cite>.</p>
+<p>For more information, see the <cite><ph conref="../conrefs.dita#pub/citadmin"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp845973.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp845973.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp845973.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp845973.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevdvlp845973" xml:lang="en-us">
 <title>Single database shutdown</title>
-<shortdesc>An application can shut down a single database within a <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<shortdesc>An application can shut down a single database within a <ph conref="../conrefs.dita#prod/productshortname"></ph> system
 and leave the rest of the system running.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Shutting down a single database</indexterm></keywords>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp846110.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp846110.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp846110.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp846110.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevdvlp846110" xml:lang="en-us">
 <title>Database-wide properties</title>
-<shortdesc>You can set many <ph conref="devconrefs.dita#prod/productshortname"></ph> properties
+<shortdesc>You can set many <ph conref="../conrefs.dita#prod/productshortname"></ph> properties
 as database-level properties. When set in this way, they are stored in the
 database and "travel" with the database unless overridden by a system property.</shortdesc>
 <prolog><metadata>
@@ -28,7 +28,7 @@
 </keywords>
 </metadata></prolog>
 <conbody>
-<p>For more information, see "Database-Wide Properties" in <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>.</p>
+<p>For more information, see "Database-Wide Properties" in <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite>.</p>
 <note>You should work with database-level properties wherever possible.</note>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp846402.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp846402.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp846402.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp846402.dita Fri Mar 30 08:17:01 2007
@@ -34,10 +34,10 @@
 <p>Two examples:</p>
 <codeblock>jdbc:derby:../otherDirectory/myDB
 
-jdbc:<ph conref="devconrefs.dita#prod/productlowercase"></ph>:c:/otherDirectory/myDB</codeblock>
-<note>Once connected, such a database becomes a part of the <ph conref="devconrefs.dita#prod/productshortname"></ph> system,
+jdbc:<ph conref="../conrefs.dita#prod/productlowercase"></ph>:c:/otherDirectory/myDB</codeblock>
+<note>Once connected, such a database becomes a part of the <ph conref="../conrefs.dita#prod/productshortname"></ph> system,
 even though it is not in the system directory. This means that it takes on
-the system-wide properties of the system and no other instance of <ph conref="devconrefs.dita#prod/productshortname"></ph> should
+the system-wide properties of the system and no other instance of <ph conref="../conrefs.dita#prod/productshortname"></ph> should
 access that database. It is recommended that you connect to databases only
 in the system directory.</note>
 </conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp91854.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp91854.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp91854.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp91854.dita Fri Mar 30 08:17:01 2007
@@ -33,15 +33,15 @@
 the database relative to the directory in the classpath. You can use the classpath
 subprotocol if such a database is ambiguous within the directory system. See <xref
 href="rdevdvlp38881.dita#rdevdvlp38881"></xref> for more information.</p>
-<p>For example, for a database called <i>sample</i> in <i>C:\<ph conref="devconrefs.dita#prod/productlowercase"></ph>\demo\databases</i>,
-you can put the <i>C:\<ph conref="devconrefs.dita#prod/productlowercase"></ph>\demo\databases</i> directory
+<p>For example, for a database called <i>sample</i> in <i>C:\<ph conref="../conrefs.dita#prod/productlowercase"></ph>\demo\databases</i>,
+you can put the <i>C:\<ph conref="../conrefs.dita#prod/productlowercase"></ph>\demo\databases</i> directory
 in the classpath and access <i>sample</i> like this:</p>
 <codeblock>
 jdbc:derby:/sample
 </codeblock>
 <p>The forward slash is required before <i>sample</i> to indicate that it
-is relative to <i>C:\<ph conref="devconrefs.dita#prod/productlowercase"></ph>\demo\databases</i> directory.</p>
-<p>If only <i>C:\<ph conref="devconrefs.dita#prod/productlowercase"></ph></i> were
+is relative to <i>C:\<ph conref="../conrefs.dita#prod/productlowercase"></ph>\demo\databases</i> directory.</p>
+<p>If only <i>C:\<ph conref="../conrefs.dita#prod/productlowercase"></ph></i> were
 in the class path, you could access <i>sample</i> (read-only) like this:</p>
 <codeblock>
 jdbc:derby:/demo/databases/sample

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp96597.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp96597.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp96597.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp96597.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
 -->
 <concept id="cdevdvlp96597" xml:lang="en-us">
 <title>One Derby instance for each Java Virtual Machine</title>
-<shortdesc>You could potentially have two instances of a <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<shortdesc>You could potentially have two instances of a <ph conref="../conrefs.dita#prod/productshortname"></ph> system
 (JVM) running on the same machine at the same time. Each instance must run
-in a different JVM. Two separate instances of <ph conref="devconrefs.dita#prod/productshortname"></ph> must
+in a different JVM. Two separate instances of <ph conref="../conrefs.dita#prod/productshortname"></ph> must
 not access the same database.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Multiple JVMs accessing<indexterm>prohibition of</indexterm></indexterm>
@@ -31,8 +31,8 @@
 </metadata></prolog>
 <conbody>
 <p>For example, in an embedded environment, an application that accesses <ph
-conref="devconrefs.dita#prod/productshortname"></ph> databases starts up the
-local JDBC driver, which starts up an instance of <ph conref="devconrefs.dita#prod/productshortname"></ph>.
+conref="../conrefs.dita#prod/productshortname"></ph> databases starts up the
+local JDBC driver, which starts up an instance of <ph conref="../conrefs.dita#prod/productshortname"></ph>.
 If you start another application, such as ij, and connect to the same database,
 severe database corruption can result. See <xref href="cdevdvlp20458.dita#cdevdvlp20458"></xref>.</p>
 </conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevin10613.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevin10613.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevin10613.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevin10613.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevin10613" xml:lang="en-us">
 <title>Localizing Derby</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> offers
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> offers
 support for locales.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Localization</indexterm><indexterm>Internationalization</indexterm>
@@ -30,13 +30,13 @@
 <p>The word <i>locale</i> in the Java platform refers to an instance of a
 class that identifies a particular combination of language and region. If
 a Java class varies its behavior according to <i>locale</i>, it is said to
-be locale-sensitive. <ph conref="devconrefs.dita#prod/productshortname"></ph> provides
+be locale-sensitive. <ph conref="../conrefs.dita#prod/productshortname"></ph> provides
 some support for locales for databases and other components such as the tools
 and the installer.</p>
 <p>It also provides a feature to support databases in many different languages,
 a feature which is independent of a particular territory.</p>
 <p>When you create or upgrade a database, you can use the territory attribute
 to associate a non-default territory with the database. For information about
-how to use the territory attribute, see the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
+how to use the territory attribute, see the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevin38113.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevin38113.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevin38113.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevin38113.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
 <concept id="cdevin38113" xml:lang="en-us">
 <title>Messages libraries</title>
 <shortdesc>The following list describes the items required in order for <ph
-conref="devconrefs.dita#prod/productshortname"></ph> to provide localized
+conref="../conrefs.dita#prod/productshortname"></ph> to provide localized
 messages.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Locales<indexterm>special library requirements</indexterm></indexterm>
@@ -29,37 +29,37 @@
 </metadata></prolog>
 <conbody>
 <ul>
-<li>You must have the locale-specific <ph conref="devconrefs.dita#prod/productshortname"></ph> jar
-file. <ph conref="devconrefs.dita#prod/productshortname"></ph> provides such
+<li>You must have the locale-specific <ph conref="../conrefs.dita#prod/productshortname"></ph> jar
+file. <ph conref="../conrefs.dita#prod/productshortname"></ph> provides such
 jars for only some locales. You will find the locale jar files in the /lib
-directory in your <ph conref="devconrefs.dita#prod/productshortname"></ph> installation.</li>
-<li>The locale-specific <ph conref="devconrefs.dita#prod/productshortname"></ph> jar
+directory in your <ph conref="../conrefs.dita#prod/productshortname"></ph> installation.</li>
+<li>The locale-specific <ph conref="../conrefs.dita#prod/productshortname"></ph> jar
 file must be in the classpath.</li>
 </ul>
-<p>The locale-specific <ph conref="devconrefs.dita#prod/productshortname"></ph> jar
-file is named <i><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_ll_CC.jar</i>,
+<p>The locale-specific <ph conref="../conrefs.dita#prod/productshortname"></ph> jar
+file is named <i><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_ll_CC.jar</i>,
 where<i> ll</i> is the two-letter code for language, and <i>CC</i> is the
 two-letter code for country. For example, the name of the jar file for error
-messages for the German locale is <codeph><i><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_de_DE.jar.</i></codeph></p>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> supports the following
+messages for the German locale is <codeph><i><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_de_DE.jar.</i></codeph></p>
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> supports the following
 locales: <ul>
-<li><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_de_DE.jar
+<li><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_de_DE.jar
 German </li>
-<li><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_es.jar
+<li><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_es.jar
 - Spanish </li>
-<li><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_fr.jar
+<li><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_fr.jar
 - French </li>
-<li><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_it.jar
+<li><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_it.jar
 - Italian </li>
-<li><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_ja_JP.jar
+<li><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_ja_JP.jar
 - Japanese </li>
-<li><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_ko_KR.jar
+<li><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_ko_KR.jar
 - Korean </li>
-<li><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_pt_BR.jar
+<li><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_pt_BR.jar
 - Brazilian Portuguese </li>
-<li><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_zh_CN.jar
+<li><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_zh_CN.jar
 - Simplified Chinese </li>
-<li><ph conref="devconrefs.dita#prod/productlowercase"></ph>Locale_zh_TW.jar
+<li><ph conref="../conrefs.dita#prod/productlowercase"></ph>Locale_zh_TW.jar
 - Traditional Chinese</li>
 </ul></p>
 </conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevin55108.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevin55108.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevin55108.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevin55108.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevin55108" xml:lang="en-us">
 <title>Other components</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> also provides
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> also provides
 locale support for the following components.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Error messages<indexterm>localized</indexterm></indexterm>
@@ -30,15 +30,15 @@
 <ul>
 <li>Database error messages are in the language of the locale, if support
 is explicitly provided for that locale with a special library.   <p>For example, <ph
-conref="devconrefs.dita#prod/productshortname"></ph> explicitly supports Spanish-language
+conref="../conrefs.dita#prod/productshortname"></ph> explicitly supports Spanish-language
 error messages. If a database's locale is set to one of the Spanish-language
-locales, <ph conref="devconrefs.dita#prod/productshortname"></ph> returns
+locales, <ph conref="../conrefs.dita#prod/productshortname"></ph> returns
 error messages in the Spanish language.</p> </li>
-<li>The <ph conref="devconrefs.dita#prod/productshortname"></ph> tools. In
+<li>The <ph conref="../conrefs.dita#prod/productshortname"></ph> tools. In
 the case of the tools, locale support includes locale-specific interface and
 error messages and localized data display.   <p>For more information about
-localization of the <ph conref="devconrefs.dita#prod/productshortname"></ph> tools,
-see the <cite><ph conref="devconrefs.dita#pub/citutilities"></ph></cite>. </p></li>
+localization of the <ph conref="../conrefs.dita#prod/productshortname"></ph> tools,
+see the <cite><ph conref="../conrefs.dita#pub/citutilities"></ph></cite>. </p></li>
 </ul>
 <p>Localized messages require special libraries.</p>
 <p>The locale of the error messages and of the tools is not determined by
@@ -48,6 +48,6 @@
 messages would not be returned in the language of the database's locale but
 in the language of the default locale instead.</p>
 <note>You can override the default locale for ij with a property on the JVM.
-For more information, see the <cite><ph conref="devconrefs.dita#pub/citutilities"></ph></cite>.</note>
+For more information, see the <cite><ph conref="../conrefs.dita#pub/citutilities"></ph></cite>.</note>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevin71274.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevin71274.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevin71274.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevin71274.dita Fri Mar 30 08:17:01 2007
@@ -20,14 +20,14 @@
 -->
 <concept id="cdevin71274" xml:lang="en-us">
 <title>SQL parser support for Unicode</title>
-<shortdesc>To support users in many different languages, <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+<shortdesc>To support users in many different languages, <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
 SQL parser understands all Unicode characters and allows any Unicode character
 or number to be used in an identifier.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Unicode support</indexterm></keywords>
 </metadata></prolog>
 <conbody>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> does not attempt
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> does not attempt
 to ensure that the characters in identifiers are valid in the database's locale.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevresman19524.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevresman19524.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevresman19524.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevresman19524.dita Fri Mar 30 08:17:01 2007
@@ -32,24 +32,24 @@
 </keywords>
 </metadata></prolog>
 <conbody>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> is a J2EE-conformant
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> is a J2EE-conformant
 component in a distributed J2EE system. As such, it is one part of a larger
 system that includes, among other things, a JNDI server, a connection pool
 module, a transaction manager, a resource manager, and user applications.
-Within this system, <ph conref="devconrefs.dita#prod/productshortname"></ph> can
+Within this system, <ph conref="../conrefs.dita#prod/productshortname"></ph> can
 serve as the resource manager.</p>
 <p>For more information on J2EE and how to work in this environment, see the
 J2EE specification available at <synph><var>http://java.sun.com/j2ee/docs.html</var></synph>.</p>
-<note>This chapter does not show you how to use <ph conref="devconrefs.dita#prod/productshortname"></ph> as
-a Resource Manager. Instead, it provides details specific to <ph conref="devconrefs.dita#prod/productshortname"></ph> that
+<note>This chapter does not show you how to use <ph conref="../conrefs.dita#prod/productshortname"></ph> as
+a Resource Manager. Instead, it provides details specific to <ph conref="../conrefs.dita#prod/productshortname"></ph> that
 are not covered in the specification. This information is useful to programmers
 developing other modules in a distributed J2EE system, not to end-user application
 developers.</note>
 <p>In order to qualify as a resource manager in a J2EE system, J2EE requires
 these basic areas of support. These three areas of support involve implementation
 of APIS and are described in "J2EE Compliance: Java Transaction API and javax.sql
-Extensions" in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
-<p>This chapter describes the <ph conref="devconrefs.dita#prod/productshortname"></ph> classes
+Extensions" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
+<p>This chapter describes the <ph conref="../conrefs.dita#prod/productshortname"></ph> classes
 that implement the APIs and provides some implementation-specific details.</p>
 <note>All of the classes described in this chapter require a Java 2 Platform,
 Standard Edition, v 1.2 (J2SE) or higher environment.</note>

Modified: db/derby/docs/trunk/src/devguide/cdevresman89722.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevresman89722.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevresman89722.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevresman89722.dita Fri Mar 30 08:17:01 2007
@@ -45,7 +45,7 @@
 javax.sql.ConnectionPoolDataSource cpds = new EmbeddedConnectionPoolDataSource(); 
 javax.sql.DataSource ds = new EmbeddedDataSource(); 
 javax.sql.XADataSource xads = new EmbeddedXADataSource();</codeblock>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> provides six properties
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> provides six properties
 for a <i>DataSource</i>. These properties are in <i>org.apache.derby.jdbc.EmbeddedDataSource</i>.
 They are:</p>
 <ul>
@@ -68,8 +68,8 @@
 <li><i>Description</i>   <p>Optional. Description of the data source. Not
 used by the data source object. Used for informational purpose only. </p></li>
 <li><i>connectionAttributes</i>   <p>Optional. Connection attributes specific
-to <ph conref="devconrefs.dita#prod/productshortname"></ph>. See the <cite><ph
-conref="devconrefs.dita#pub/citref"></ph></cite> for a more information about
+to <ph conref="../conrefs.dita#prod/productshortname"></ph>. See the <cite><ph
+conref="../conrefs.dita#pub/citref"></ph></cite> for a more information about
 the attributes. </p></li>
 </ul>
 </conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevresman92946.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevresman92946.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevresman92946.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevresman92946.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
 <concept id="cdevresman92946" xml:lang="en-us">
 <title>Shutting down or creating a database</title>
 <shortdesc>If you need to shut down or create a database, it is easiest just
-to work with the <ph conref="devconrefs.dita#prod/productshortname"></ph>-specific
+to work with the <ph conref="../conrefs.dita#prod/productshortname"></ph>-specific
 implementations of interfaces, as shown in these examples.</shortdesc>
 <prolog></prolog>
 <conbody>
@@ -29,7 +29,7 @@
 
 
 <b>// example of setting property directory using </b>
-// <b><ph conref="devconrefs.dita#prod/productshortname"></ph> 's </b>XADataSource object
+// <b><ph conref="../conrefs.dita#prod/productshortname"></ph> 's </b>XADataSource object
 import org.apache.derby.jdbc.EmbeddedXADataSource;
 import javax.sql.XADataSource;
 <b>// dbname is the database name
@@ -42,7 +42,7 @@
     // EmbeddedXADataSource40.
     //</b>
     EmbeddedXADataSource xads = new EmbeddedXADataSource();
-<b>    // use <ph conref="devconrefs.dita#prod/productshortname"></ph> 's setDatabaseName call</b>
+<b>    // use <ph conref="../conrefs.dita#prod/productshortname"></ph> 's setDatabaseName call</b>
     xads.setDatabaseName(dbname);
     if (create)
         xads.setCreateDatabase("create");

Modified: db/derby/docs/trunk/src/devguide/cdevspecial.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevspecial.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevspecial.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevspecial.dita Fri Mar 30 08:17:01 2007
@@ -19,7 +19,7 @@
 -->
 <concept id="cdevspecial" xml:lang="en-us">
 <title>Derby server-side programming</title>
-<shortdesc>This section discusses special programming for <ph conref="devconrefs.dita#prod/productshortname"></ph>.</shortdesc>
+<shortdesc>This section discusses special programming for <ph conref="../conrefs.dita#prod/productshortname"></ph>.</shortdesc>
 <conbody>
 <p>These features include such programming as database-side JDBC procedures
 and triggers.</p>

Modified: db/derby/docs/trunk/src/devguide/cdevspecial27163.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevspecial27163.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevspecial27163.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevspecial27163.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevspecial27163" xml:lang="en-us">
 <title>Programming trigger actions</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> allows
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> allows
 you to create triggers. When you create a trigger, you define an action or
 set of actions that are executed when a database event occurs on a specified
 table. A <i>database event</i> is a delete, insert, or update operation.</shortdesc>
@@ -32,7 +32,7 @@
 <p>For example, if you define a trigger for a delete on a particular table,
 the trigger action is executed whenever someone deletes a row or rows from
 the table.</p>
-<p>The <codeph>CREATE TRIGGER</codeph> statement in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite> goes
+<p>The <codeph>CREATE TRIGGER</codeph> statement in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite> goes
 into detail of the complete <codeph>CREATE TRIGGER</codeph> syntax. This section
 provides information on defining the trigger action itself, which is only
 one aspect of creating triggers.</p>

Modified: db/derby/docs/trunk/src/devguide/cdevspecial41728.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevspecial41728.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevspecial41728.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevspecial41728.dita Fri Mar 30 08:17:01 2007
@@ -33,14 +33,14 @@
 (such as deadlocks), this "hiding" of the exception causes unexpected problems.</p>
 <p>This is because errors of transaction severity roll back work already done
 by a transaction (not just the piece executed by the called method) and silently
-begin a new transaction. When the method execution is complete, <ph conref="devconrefs.dita#prod/productshortname"></ph> detects
+begin a new transaction. When the method execution is complete, <ph conref="../conrefs.dita#prod/productshortname"></ph> detects
 that the outer statement was invalidated by a deadlock and rolls back any
 work done<i> in the new transaction</i> as well. This is the expected behavior,
 because all the statements in between explicit commits should be treated atomically;
-the new transaction implicitly begun by <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+the new transaction implicitly begun by <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
 rollback was not intended by the application designer.</p>
 <p>However, this is not the same behavior that would happen if the method
-were invoked in the application. In that situation, <ph conref="devconrefs.dita#prod/productshortname"></ph> would
+were invoked in the application. In that situation, <ph conref="../conrefs.dita#prod/productshortname"></ph> would
 roll back the work done by the transaction and silently begin a new transaction.
 Work in the new transaction would not be rolled back when the method returned.
 However, coding the application in that way means that the transaction did

Modified: db/derby/docs/trunk/src/devguide/cdevspecial42117.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevspecial42117.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevspecial42117.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevspecial42117.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 <concept id="cdevspecial42117" xml:lang="en-us">
 <title>Programming database-side JDBC procedures</title>
 <shortdesc>Methods invoked within an application are called application-side
-methods. Methods invoked within <ph conref="devconrefs.dita#prod/productshortname"></ph> are
+methods. Methods invoked within <ph conref="../conrefs.dita#prod/productshortname"></ph> are
 called database-side procedures.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Database-side JDBC procedures</indexterm></keywords>

Modified: db/derby/docs/trunk/src/devguide/cdevspecial45786.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevspecial45786.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevspecial45786.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevspecial45786.dita Fri Mar 30 08:17:01 2007
@@ -21,14 +21,14 @@
 <concept id="cdevspecial45786" xml:lang="en-us">
 <title>User-defined SQLExceptions</title>
 <shortdesc>When the execution of a database-side method raises an error, <ph
-conref="devconrefs.dita#prod/productshortname"></ph> wraps that exception
+conref="../conrefs.dita#prod/productshortname"></ph> wraps that exception
 in an <i>SQLException</i> with an <codeph><i>SQLState</i></codeph> of 38000.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>SQLExceptions<indexterm>user-defined (38001-38999)</indexterm></indexterm>
 </keywords>
 </metadata></prolog>
 <conbody>
-<p>You can avoid having <ph conref="devconrefs.dita#prod/productshortname"></ph> wrap
+<p>You can avoid having <ph conref="../conrefs.dita#prod/productshortname"></ph> wrap
 the exception if:</p>
 <ul>
 <li>The exception is an <i>SQLException</i></li>

Modified: db/derby/docs/trunk/src/devguide/cdevspecial53165.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevspecial53165.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevspecial53165.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevspecial53165.dita Fri Mar 30 08:17:01 2007
@@ -34,7 +34,7 @@
 		WHERE YEAR(flight_date) &lt; 2005);) </codeblock>
 <p>A trigger action does have some limitations, though; for example, it cannot
 contain dynamic parameters or alter the table on which the trigger is defined.
-See "TriggerAction" in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite> for
+See "TriggerAction" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite> for
 details. </p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevspecial67260.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevspecial67260.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevspecial67260.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevspecial67260.dita Fri Mar 30 08:17:01 2007
@@ -34,9 +34,9 @@
 <li>the "after" values of the rows being changed (the values to which the
 database event is setting them)</li>
 </ul>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> provides transition
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> provides transition
 variables and transition tables for a trigger action to access these values.
 See "Referencing Old and New Values: The Referencing Clause" in the <cite><ph
-conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
+conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevspecial76763.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevspecial76763.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevspecial76763.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevspecial76763.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevspecial76763" xml:lang="en-us">
 <title>Performing referential actions</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> provides
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> provides
 referential actions. Examples in this section are included to illustrate how
 to write triggers.</shortdesc>
 <prolog><metadata>
@@ -31,7 +31,7 @@
 </metadata></prolog>
 <conbody>
 <p>You can choose to use standard SQL referential integrity to obtain this
-functionality, rather than writing triggers. See the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite> for
+functionality, rather than writing triggers. See the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite> for
 more information on referential integrity.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevspecial847513.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevspecial847513.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevspecial847513.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevspecial847513.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevspecial847513" xml:lang="en-us">
 <title>Invoking a procedure using the CALL command</title>
-<shortdesc>If a procedure uses only IN parameters, <ph conref="devconrefs.dita#prod/productshortname"></ph> can
+<shortdesc>If a procedure uses only IN parameters, <ph conref="../conrefs.dita#prod/productshortname"></ph> can
 execute the procedure by using the SQL CALL command. A stored procedure with
 IN, OUT, or INOUT parameters can be invoked from a client application by using
 the CallableStatement method.</shortdesc>

Modified: db/derby/docs/trunk/src/devguide/cdevstandards806118.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstandards806118.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstandards806118.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstandards806118.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
 -->
 <concept id="cdevstandards806118" xml:lang="en-us">
 <title>Derby and standards</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> adheres
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> adheres
 to SQL99 standards wherever possible. This section describes those
-features currently in <ph conref="devconrefs.dita#prod/productshortname"></ph> that
+features currently in <ph conref="../conrefs.dita#prod/productshortname"></ph> that
 are not standard; these features are currently being evaluated and might be
 removed in future releases.</shortdesc>
 <prolog><metadata>
@@ -32,19 +32,19 @@
 </keywords>
 </metadata></prolog>
 <conbody>
-<p>This section describes those parts of <ph conref="devconrefs.dita#prod/productshortname"></ph> that
+<p>This section describes those parts of <ph conref="../conrefs.dita#prod/productshortname"></ph> that
 are non-standard or not typical for a database system.</p>
 <dl>
 <dlentry>
 <dt>ALTER TABLE syntax</dt>
-<dd><ph conref="devconrefs.dita#prod/productshortname"></ph> uses a
+<dd><ph conref="../conrefs.dita#prod/productshortname"></ph> uses a
 slightly different ALTER TABLE syntax for altering column defaults. While
-SQL99 uses DROP and SET, <ph conref="devconrefs.dita#prod/productshortname"></ph>
+SQL99 uses DROP and SET, <ph conref="../conrefs.dita#prod/productshortname"></ph>
 uses DEFAULT.</dd>
 </dlentry>
 <dlentry>
 <dt>Calling functions and procedures</dt>
-<dd><ph conref="devconrefs.dita#prod/productshortname"></ph> supports
+<dd><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
 the CALL (procedure) statement for calling external procedures declared by
 the CREATE PROCEDURE statement. Built-in functions and user-defined functions
 declared with the CREATE FUNCTION command can be called as part of an SQL
@@ -52,33 +52,33 @@
 </dlentry>
 <dlentry>
 <dt>CLOB and BLOB data types</dt>
-<dd><ph conref="devconrefs.dita#prod/productshortname"></ph> supports the
+<dd><ph conref="../conrefs.dita#prod/productshortname"></ph> supports the
 standard CLOB and BLOB data types. BLOB and CLOB values are limited to a
 maximum of 2,147,483,647 characters.</dd>
 </dlentry>
 <dlentry>
 <dt>Cursors</dt>
-<dd><ph conref="devconrefs.dita#prod/productshortname"></ph> uses JDBC's result
+<dd><ph conref="../conrefs.dita#prod/productshortname"></ph> uses JDBC's result
 sets, and does not provide SQL for manipulating cursors except for positioned
-update and delete. <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+update and delete. <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
 scrollable insensitive cursors are provided through JDBC, not through SQL
 commands.</dd>
 </dlentry>
 <dlentry>
 <dt>DECIMAL max precision</dt>
-<dd>For <ph conref="devconrefs.dita#prod/productshortname"></ph>, the maximum
+<dd>For <ph conref="../conrefs.dita#prod/productshortname"></ph>, the maximum
 precision for DECIMAL columns is 31 digits. SQL99 does not require a specific
 maximum precision for decimals, but most products have a maximum precision of
 15-32 digits.</dd>
 </dlentry>
 <dlentry>
 <dt>Dynamic SQL</dt>
-<dd><ph conref="devconrefs.dita#prod/productshortname"></ph> uses JDBC's
+<dd><ph conref="../conrefs.dita#prod/productshortname"></ph> uses JDBC's
 Prepared Statement, and does not provide SQL commands for dynamic SQL.</dd>
 </dlentry>
 <dlentry>
 <dt>Expressions on LONGs</dt>
-<dd><ph conref="devconrefs.dita#prod/productshortname"></ph> permits
+<dd><ph conref="../conrefs.dita#prod/productshortname"></ph> permits
 expressions on LONG VARCHAR; however, LONG VARCHAR data types are not allowed
 in the following clauses, operations, constraints, functions, and predicates:
 <ul>
@@ -98,29 +98,29 @@
 </dlentry>
 <dlentry>
 <dt>Information schema</dt>
-<dd><ph conref="devconrefs.dita#prod/productshortname"></ph> uses its own system
+<dd><ph conref="../conrefs.dita#prod/productshortname"></ph> uses its own system
 catalog that can be accessed using standard JDBC DatabaseMetadata calls.
-<ph conref="devconrefs.dita#prod/productshortname"></ph> does not provide the
+<ph conref="../conrefs.dita#prod/productshortname"></ph> does not provide the
 standard Information Schema views.</dd>
 </dlentry>
 <dlentry>
 <dt>NOT NULL characteristic</dt>
 <dd>The SQL standard says NOT NULL is a constraint, and can be named and viewed
 in the information schema as such.
-<ph conref="devconrefs.dita#prod/productshortname"></ph> does not provide naming
+<ph conref="../conrefs.dita#prod/productshortname"></ph> does not provide naming
 for NOT NULL, nor does it present it as a constraint in the information schema,
 only as a characteristic of the column.</dd>
 </dlentry>
 <dlentry>
 <dt>Stored routines and PSM</dt>
-<dd><ph conref="devconrefs.dita#prod/productshortname"></ph> supports external
+<dd><ph conref="../conrefs.dita#prod/productshortname"></ph> supports external
 procedures using the Java programming language. Procedures are managed using the
 CREATE PROCEDURE and DROP PROCEDURE statements.</dd>
 </dlentry>
 <dlentry>
 <dt>Transactions</dt>
-<dd>All operations in <ph conref="devconrefs.dita#prod/productshortname"></ph>
-are transactional. <ph conref="devconrefs.dita#prod/productshortname"></ph>
+<dd>All operations in <ph conref="../conrefs.dita#prod/productshortname"></ph>
+are transactional. <ph conref="../conrefs.dita#prod/productshortname"></ph>
 supports transaction control using JDBC 3.0 Connection methods. This includes
 support for savepoints and for the four JDBC transaction isolation levels. The
 only SQL command provided for transaction control is SET TRANSACTION ISOLATION.
@@ -129,7 +129,7 @@
 <dlentry>
 <dt>Unique constraints and nulls</dt>
 <dd>The SQL standard defines that unique constraints on nullable columns
-allow any number of nulls; <ph conref="devconrefs.dita#prod/productshortname"></ph> does
+allow any number of nulls; <ph conref="../conrefs.dita#prod/productshortname"></ph> does
 not permit unique constraints on nullable columns.</dd>
 </dlentry>
 </dl>

Modified: db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevstandardsxml" xml:lang="en-us">
 <title>XML data types and operators</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> supports
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
 the XML data type and a set of operators that work with the XML data type.
 The XML data type and operators are based on a small subset of the SQL/XML
 specification. </shortdesc>
@@ -42,27 +42,27 @@
 <p>The XML data type is not allowed in any of the clauses or operations that
 are described in the section on expressions on LONG data types in 
 <xref href="cdevstandards806118.dita#cdevstandards806118"></xref>.</p>
-<p>For the XML operators to work properly, <ph conref="devconrefs.dita#prod/productshortname"></ph> requires
+<p>For the XML operators to work properly, <ph conref="../conrefs.dita#prod/productshortname"></ph> requires
 that a JAXP parser, such as Apache Xerces, and Apache Xalan are included in
 the Java classpath. If either the parser or Xalan are missing from the classpath, <ph
-conref="devconrefs.dita#prod/productshortname"></ph> disallows any XML-related
+conref="../conrefs.dita#prod/productshortname"></ph> disallows any XML-related
 operations.  </p>
 <p>To see a list of the versions of the JAXP implementation and of Apache
-Xalan that have been tested with <ph conref="devconrefs.dita#prod/productshortname"></ph> XML
-support, see to the <ph conref="devconrefs.dita#prod/productshortname"></ph> release
+Xalan that have been tested with <ph conref="../conrefs.dita#prod/productshortname"></ph> XML
+support, see to the <ph conref="../conrefs.dita#prod/productshortname"></ph> release
 notes. The release notes are available from the Apache Derby Downloads page.</p>
 <note>Most Java virtual machines (JVMs) that are version 1.4 or later have
 a JAXP parser embedded in the JVM. If you are using one of these JVMs, you
 do not need to add any other JAXP classes to your classpath. Additionally,
 if the JVM that you are using includes an embedded version of Xalan, you should
 confirm that the version of Xalan satisfies the minimum requirements for <ph
-conref="devconrefs.dita#prod/productshortname"></ph>. For example, if your
+conref="../conrefs.dita#prod/productshortname"></ph>. For example, if your
 JVM is Sun JDK 1.4.2, you must override the version of Xalan in the JVM with
 a newer version. Use Java's Endorsed Standards Override Mechanisms described
 at http://java.sun.com/j2se/1.4.2/docs/guide/standards/ to override the version
 of Xalan. <p>If the JVM that you are using does not have a JAXP parser or
 a version of Xalan, you can add external versions of those classes in your
-classpath and <ph conref="devconrefs.dita#prod/productshortname"></ph> will
+classpath and <ph conref="../conrefs.dita#prod/productshortname"></ph> will
 pick up those classes.</p></note>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevstart16043.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstart16043.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstart16043.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstart16043.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevstart16043" xml:lang="en-us">
 <title>The installation directory</title>
-<shortdesc>You may install the <ph conref="devconrefs.dita#prod/productshortname"></ph> software
+<shortdesc>You may install the <ph conref="../conrefs.dita#prod/productshortname"></ph> software
 in a directory of your choice.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Installation directory<indexterm>layout of</indexterm></indexterm>
@@ -30,25 +30,25 @@
 </metadata></prolog>
 <conbody>
 <p>See the <codeph>index.html</codeph> file for pointers to information on <ph
-conref="devconrefs.dita#prod/productshortname"></ph>.</p>
+conref="../conrefs.dita#prod/productshortname"></ph>.</p>
 <p>The distribution includes setup scripts that use an environment
-variable called <ph conref="devconrefs.dita#prod/productinstallpath"></ph>.
-The variable's value is set to the <ph conref="devconrefs.dita#prod/productshortname"></ph> base
+variable called <ph conref="../conrefs.dita#prod/productinstallpath"></ph>.
+The variable's value is set to the <ph conref="../conrefs.dita#prod/productshortname"></ph> base
 directory.</p>
-<codeblock>C:&gt;echo %<ph conref="devconrefs.dita#prod/productinstallpath"></ph>%
-C:\<ph conref="devconrefs.dita#prod/productinstallpath"></ph></codeblock>
-<p>If you want to set your own environment, <cite><ph conref="devconrefs.dita#pub/citgetstart"></ph></cite> instructs
-you on setting its value to the directory in which you installed the <ph conref="devconrefs.dita#prod/productshortname"></ph> software.</p>
-<p>The distribution for <ph conref="devconrefs.dita#prod/productshortname"></ph> contains
+<codeblock>C:&gt;echo %<ph conref="../conrefs.dita#prod/productinstallpath"></ph>%
+C:\<ph conref="../conrefs.dita#prod/productinstallpath"></ph></codeblock>
+<p>If you want to set your own environment, <cite><ph conref="../conrefs.dita#pub/citgetstart"></ph></cite> instructs
+you on setting its value to the directory in which you installed the <ph conref="../conrefs.dita#prod/productshortname"></ph> software.</p>
+<p>The distribution for <ph conref="../conrefs.dita#prod/productshortname"></ph> contains
 all the files you need, including the documentation set, some example applications,
 and a sample database.</p>
 <p>Details about the installation:</p>
 <ul>
 <li><i>index.html </i>in the top-level directory is the top page for the on-line
 documentation.</li>
-<li><i>RELEASE-NOTES.html</i>, in the top-level <ph conref="devconrefs.dita#prod/productshortname"></ph> base
+<li><i>RELEASE-NOTES.html</i>, in the top-level <ph conref="../conrefs.dita#prod/productshortname"></ph> base
 directory, contains important last-minute information. <i>Read it first</i>.</li>
-<li><i>/bin</i> contains utilities and scripts for running <ph conref="devconrefs.dita#prod/productshortname"></ph>. </li>
+<li><i>/bin</i> contains utilities and scripts for running <ph conref="../conrefs.dita#prod/productshortname"></ph>. </li>
 <li><i>/demo</i> contains some sample applications, useful scripts, and prebuilt
 databases.   <ul>
 <li><i>/databases</i> includes prebuilt sample databases.</li>
@@ -56,9 +56,9 @@
 </ul></li>
 <li><i>/docs</i> contains the on-line documentation (including this document).</li>
 <li><i>/javadoc</i> contains the documented APIs for the public classes and
-interfaces. Typically, you use the JDBC interface to interact with <ph conref="devconrefs.dita#prod/productshortname"></ph>;
+interfaces. Typically, you use the JDBC interface to interact with <ph conref="../conrefs.dita#prod/productshortname"></ph>;
 however, you can use some of these additional classes in certain situations.</li>
-<li><i>/lib</i> contains the <ph conref="devconrefs.dita#prod/productshortname"></ph> libraries.</li>
+<li><i>/lib</i> contains the <ph conref="../conrefs.dita#prod/productshortname"></ph> libraries.</li>
 </ul>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevstart18978.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstart18978.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstart18978.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstart18978.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevstart18978" xml:lang="en-us">
 <title>Derby and JVMs</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> is a database
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> is a database
 engine written completely in Java; it will run in any JVM, version 1.3 or
 higher.</shortdesc>
 <prolog><metadata>

Modified: db/derby/docs/trunk/src/devguide/cdevstart19524.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstart19524.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstart19524.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstart19524.dita Fri Mar 30 08:17:01 2007
@@ -25,12 +25,12 @@
 <prolog></prolog>
 <conbody>
 <p>Review the <codeph>index.html</codeph> file at the top level of the <ph
-conref="devconrefs.dita#prod/productshortname"></ph> distribution
+conref="../conrefs.dita#prod/productshortname"></ph> distribution
 for pointers to reference and tutorial information about
-<ph conref="devconrefs.dita#prod/productshortname"></ph>.
+<ph conref="../conrefs.dita#prod/productshortname"></ph>.
 See the Release Notes for information on platform support, changes that may
 affect your existing applications, defect information, and recent documentation
-updates. See <cite><ph conref="devconrefs.dita#pub/citgetstart"></ph></cite> for
+updates. See <cite><ph conref="../conrefs.dita#pub/citgetstart"></ph></cite> for
 basic product descriptions, information on getting started, and directions
 for setting the path and the classpath. </p>
 </conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevstart39409.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstart39409.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstart39409.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstart39409.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevstart39409" xml:lang="en-us">
 <title>Configuring file descriptors</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> databases
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> databases
 create one file per table or index. Some operating systems limit the number
 of files an application can open at one time.</shortdesc>
 <prolog><metadata>

Modified: db/derby/docs/trunk/src/devguide/cdevstart41260.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstart41260.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstart41260.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstart41260.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevstart41260" xml:lang="en-us">
 <title>UNIX-specific issues</title>
-<shortdesc>This section discusses <ph conref="devconrefs.dita#prod/productshortname"></ph> issues
+<shortdesc>This section discusses <ph conref="../conrefs.dita#prod/productshortname"></ph> issues
 specifically related to UNIX platforms.</shortdesc>
 <prolog></prolog>
 <conbody></conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevstart813142.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstart813142.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstart813142.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstart813142.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
 <concept id="cdevstart813142" xml:lang="en-us">
 <title>Batch files and shell scripts</title>
 <shortdesc>The <i>/bin</i> directory contains scripts
-for running some of the <ph conref="devconrefs.dita#prod/productshortname"></ph> tools
+for running some of the <ph conref="../conrefs.dita#prod/productshortname"></ph> tools
 and utilities. To customize your environment, put the directory first in your
 path.</shortdesc>
 <prolog><metadata>

Modified: db/derby/docs/trunk/src/devguide/cdevstart813545.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstart813545.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstart813545.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstart813545.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
 <concept id="cdevstart813545" xml:lang="en-us">
 <title>Scripts</title>
 <shortdesc>Your installation contains executable script files that simplify
-invoking the <ph conref="devconrefs.dita#prod/productshortname"></ph> tools.
+invoking the <ph conref="../conrefs.dita#prod/productshortname"></ph> tools.
 On UNIX systems, these files might need to have their default protections
 set to include execute privilege.</shortdesc>
 <prolog></prolog>

Modified: db/derby/docs/trunk/src/devguide/cdevstart98282.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstart98282.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstart98282.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstart98282.dita Fri Mar 30 08:17:01 2007
@@ -20,13 +20,13 @@
 -->
 <concept id="cdevstart98282" xml:lang="en-us">
 <title>Derby libraries and classpath</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> libraries
-are located in the /<i>lib</i> subdirectory of the <ph conref="devconrefs.dita#prod/productshortname"></ph> base
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> libraries
+are located in the /<i>lib</i> subdirectory of the <ph conref="../conrefs.dita#prod/productshortname"></ph> base
 directory. You must set the classpath on your development machine to include
 the appropriate libraries.</shortdesc>
 <prolog></prolog>
 <conbody>
-<p><cite><ph conref="devconrefs.dita#pub/citgetstart"></ph></cite><cite> </cite> explains
+<p><cite><ph conref="../conrefs.dita#pub/citgetstart"></ph></cite><cite> </cite> explains
 how to set the classpath in a development environment.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevtricks19707.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevtricks19707.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevtricks19707.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevtricks19707.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevtricks19707" xml:lang="en-us">
 <title>Retrieving the database connection URL</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> does not
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> does not
 have a built-in function that returns the name of the database. However, you
 can use <codeph>DatabaseMetaData</codeph> to return the connection URL of
 any local <codeph>Connection</codeph>.</shortdesc>

Modified: db/derby/docs/trunk/src/devguide/cdevtricks21248.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevtricks21248.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevtricks21248.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevtricks21248.dita Fri Mar 30 08:17:01 2007
@@ -28,8 +28,8 @@
 <indexterm>Identity column<indexterm>definition</indexterm></indexterm></keywords>
 </metadata></prolog>
 <conbody>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> provides autoincrement
-as a built-in feature; see CREATE TABLE statement in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> provides autoincrement
+as a built-in feature; see CREATE TABLE statement in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
 <p>Below is an example that shows how to use an identity column to create
 the MAP_ID column of the MAPS table in the <i>toursDB database</i>.</p>
 <codeblock>CREATE TABLE MAPS

Modified: db/derby/docs/trunk/src/devguide/cdevtricks23426.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevtricks23426.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevtricks23426.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevtricks23426.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
 <concept id="cdevtricks23426" xml:lang="en-us">
 <title>Using third-party tools</title>
 <shortdesc>You can hook into any JDBC tool with just our JDBC Driver class
-name (<i>org.apache.derby.jdbc.EmbeddedDriver</i>) and <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+name (<i>org.apache.derby.jdbc.EmbeddedDriver</i>) and <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
 JDBC connection URL.</shortdesc>
 <prolog></prolog>
 <conbody></conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevtricks807337.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevtricks807337.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevtricks807337.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevtricks807337.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevtricks807337" xml:lang="en-us">
 <title>Multiple rows</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> supports
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
 the complete SQL-92 VALUES clause; this is very handy in several cases.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Multiple rows VALUES clause</indexterm></keywords>

Modified: db/derby/docs/trunk/src/devguide/cdevtricks807400.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevtricks807400.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevtricks807400.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevtricks807400.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
 -->
 <concept id="cdevtricks807400" xml:lang="en-us">
 <title>Creating empty queries</title>
-<shortdesc>You may need <ph conref="devconrefs.dita#prod/productshortname"></ph> to
+<shortdesc>You may need <ph conref="../conrefs.dita#prod/productshortname"></ph> to
 create "empty" queries in existing applications for filling in bits of functionality
-that <ph conref="devconrefs.dita#prod/productshortname"></ph> does not supply.</shortdesc>
+that <ph conref="../conrefs.dita#prod/productshortname"></ph> does not supply.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Creating empty queries</indexterm></keywords>
 </metadata></prolog>

Modified: db/derby/docs/trunk/src/devguide/cdevupgrades.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevupgrades.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevupgrades.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevupgrades.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 <concept id="cdevupgrades" xml:lang="en-us">
 <title>Upgrades</title>
 <shortdesc>To connect to a database created with a previous version of <ph
-conref="devconrefs.dita#prod/productshortname"></ph>, you must first upgrade
+conref="../conrefs.dita#prod/productshortname"></ph>, you must first upgrade
 that database.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Upgrading Derby</indexterm></keywords>
@@ -29,10 +29,10 @@
 <p>Upgrading involves writing changes to the system tables, so it is not possible
 for databases on read-only media. The upgrade process:</p>
 <ul>
-<li>marks the database as upgraded to the current release (Version <ph conref="devconrefs.dita#vers/shortversionnumber"></ph>).</li>
+<li>marks the database as upgraded to the current release (Version <ph conref="../conrefs.dita#vers/shortversionnumber"></ph>).</li>
 <li>allows use of new features.</li>
 </ul>
 <p>See the release notes for more information on upgrading your databases
-to this version of <ph conref="devconrefs.dita#prod/productshortname"></ph>.</p>
+to this version of <ph conref="../conrefs.dita#prod/productshortname"></ph>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/rdevconcepts600.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevconcepts600.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevconcepts600.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevconcepts600.dita Fri Mar 30 08:17:01 2007
@@ -49,7 +49,7 @@
 this problem with Java synchronization.</p></section>
 <section><p>If the threads each obtain their own <i>PreparedStatement</i> (with
 identical text), their <codeph><i>setXXX</i></codeph> calls do not interfere
-with each other. Moreover, <ph conref="devconrefs.dita#prod/productshortname"></ph> is
+with each other. Moreover, <ph conref="../conrefs.dita#prod/productshortname"></ph> is
 able to share the same compiled query plan between the two statements; it
 needs to maintain only separate state information. However, there is the potential
 for confusion in regard to the timing of the <i>commit</i>, since a single <i>commit</i> commits

Modified: db/derby/docs/trunk/src/devguide/rdevconcepts713.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevconcepts713.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevconcepts713.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevconcepts713.dita Fri Mar 30 08:17:01 2007
@@ -32,10 +32,10 @@
 <refbody>
 <section> <ul>
 <li>Multiple applications access a single database (possible only when <ph
-conref="devconrefs.dita#prod/productshortname"></ph> is running inside a server
+conref="../conrefs.dita#prod/productshortname"></ph> is running inside a server
 framework).</li>
 <li>A single application has more than one <i>Connection</i> to the same database.
-  <p>The way you deploy <ph conref="devconrefs.dita#prod/productshortname"></ph> affects
+  <p>The way you deploy <ph conref="../conrefs.dita#prod/productshortname"></ph> affects
 the ways applications can use multi-threading and connections, as shown in <xref
 href="rdevconcepts713.dita#rdevconcepts713/cdevconcepts40343"></xref>.</p><table
 frame="all" id="cdevconcepts40343"><title>Threading and Connection Modes</title>
@@ -52,10 +52,10 @@
 <tbody>
 <row>
 <entry colname="1"><p><i>Multi-Threaded</i></p><p>From an application, using
-a <i>single</i> <codeph><i>Connection</i></codeph> to a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+a <i>single</i> <codeph><i>Connection</i></codeph> to a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
 and issuing requests against that connection in multiple threads.</p></entry>
 <entry colname="2">Supply a single <i>Connection</i> object to separate threads. <ph
-conref="devconrefs.dita#prod/productshortname"></ph> ensures that only one
+conref="../conrefs.dita#prod/productshortname"></ph> ensures that only one
 operation is applied at a time for consistency. Server frameworks automatically
 manage multi-threaded operations..</entry>
 <entry colname="3">Server frameworks can automatically multi-thread operations.
@@ -63,24 +63,24 @@
 </row>
 <row>
 <entry colname="1"><p><i>Multi-Connection</i></p><p>From an application, using
-multiple connections to a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+multiple connections to a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
 and issuing requests against those connections on multiple threads.</p></entry>
 <entry colname="2">Create individual connections within a single application
 and use the appropriate connection for each JDBC request. The connections
 can all be to the same database, or can be to different databases in the same <ph
-conref="devconrefs.dita#prod/productshortname"></ph> system.</entry>
+conref="../conrefs.dita#prod/productshortname"></ph> system.</entry>
 <entry colname="3">Remote client applications can establish the multiple connections
 desired.</entry>
 </row>
 <row>
 <entry colname="1"><p><i>Multi-User</i></p><p>Multiple applications (or JVMs)
-accessing the same <ph conref="devconrefs.dita#prod/productshortname"></ph> database.
+accessing the same <ph conref="../conrefs.dita#prod/productshortname"></ph> database.
 Each user application has its own connection or connections to the database.</p></entry>
 <entry colname="2">Not possible. Only one application can access a database
 at a time, and only one application can access a specific system at a time.
-When using a pre-1.4 JVM, <ph conref="devconrefs.dita#prod/productshortname"></ph> might
+When using a pre-1.4 JVM, <ph conref="../conrefs.dita#prod/productshortname"></ph> might
 not prevent multiple applications from concurrently accessing the same <ph
-conref="devconrefs.dita#prod/productshortname"></ph> system, but do not allow
+conref="../conrefs.dita#prod/productshortname"></ph> system, but do not allow
 this because such access can corrupt the databases involved.</entry>
 <entry colname="3">Only one server should access a database at a time. Multiple
 remote client applications can access the same server, and thus can access



Mime
View raw message