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 [1/4] - /db/derby/docs/trunk/src/devguide/
Date Fri, 30 Mar 2007 15:17:11 GMT
Author: scotsmatrix
Date: Fri Mar 30 08:17:01 2007
New Revision: 524118

URL: http://svn.apache.org/viewvc?view=rev&rev=524118
Log:
DERBY-1590: updated the conrefs in the devguide to use the global conrefs file. Patch derby-1590-devguide.diff was contributed by Kim Haase.

Modified:
    db/derby/docs/trunk/src/devguide/cdevadvjdbc18939.dita
    db/derby/docs/trunk/src/devguide/cdevadvjdbc32436.dita
    db/derby/docs/trunk/src/devguide/cdevadvjdbc41138.dita
    db/derby/docs/trunk/src/devguide/cdevbabejgjd.dita
    db/derby/docs/trunk/src/devguide/cdevcbabejdfj.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts10914.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts14433.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts15366.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts16400.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts19173.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts19524.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts22300.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts22641.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts23810.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts24927.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts28351.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts29416.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts30291.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts30811.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts34828.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts36402.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts36881.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts41275.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts53677.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts65864.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts839085.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts840995.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts844813.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts95005.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure10983.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure12392.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure21547.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure21561.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure24366.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure24458.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure36127.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure36595.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure37241.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure37817.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure38522.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure41285.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure42374.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure51876.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure60146.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure67151.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure79358.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure863546.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure863676.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure864242.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure864642.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure864692.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure865580.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure866716.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure876908.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure88690.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure90988.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure96815.dita
    db/derby/docs/trunk/src/devguide/cdevcsecure97760.dita
    db/derby/docs/trunk/src/devguide/cdevcsecuree.dita
    db/derby/docs/trunk/src/devguide/cdevcsecuregrantrevokeaccess.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy12748.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy15325.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy15818.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy17604.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy18716.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy21645.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy23812.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy30736.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy32171.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy855368.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy855655.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy856753.dita
    db/derby/docs/trunk/src/devguide/cdevdeploy857611.dita
    db/derby/docs/trunk/src/devguide/cdevdgpref11181.dita
    db/derby/docs/trunk/src/devguide/cdevdgpref23947.dita
    db/derby/docs/trunk/src/devguide/cdevdgpref24290.dita
    db/derby/docs/trunk/src/devguide/cdevdgpref29520.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp13018.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp14839.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp17453.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp18166.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp19297.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp19524.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp21955.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp22619.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp24155.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp25174.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp25820.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp25889.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp27610.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp27715.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp30653.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp34964.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp39409.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp39943.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp40170.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp40350.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp40653.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp40724.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp42173.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp51654.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp84026.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp845973.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp846110.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp846402.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp91854.dita
    db/derby/docs/trunk/src/devguide/cdevdvlp96597.dita
    db/derby/docs/trunk/src/devguide/cdevin10613.dita
    db/derby/docs/trunk/src/devguide/cdevin38113.dita
    db/derby/docs/trunk/src/devguide/cdevin55108.dita
    db/derby/docs/trunk/src/devguide/cdevin71274.dita
    db/derby/docs/trunk/src/devguide/cdevresman19524.dita
    db/derby/docs/trunk/src/devguide/cdevresman89722.dita
    db/derby/docs/trunk/src/devguide/cdevresman92946.dita
    db/derby/docs/trunk/src/devguide/cdevspecial.dita
    db/derby/docs/trunk/src/devguide/cdevspecial27163.dita
    db/derby/docs/trunk/src/devguide/cdevspecial41728.dita
    db/derby/docs/trunk/src/devguide/cdevspecial42117.dita
    db/derby/docs/trunk/src/devguide/cdevspecial45786.dita
    db/derby/docs/trunk/src/devguide/cdevspecial53165.dita
    db/derby/docs/trunk/src/devguide/cdevspecial67260.dita
    db/derby/docs/trunk/src/devguide/cdevspecial76763.dita
    db/derby/docs/trunk/src/devguide/cdevspecial847513.dita
    db/derby/docs/trunk/src/devguide/cdevstandards806118.dita
    db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita
    db/derby/docs/trunk/src/devguide/cdevstart16043.dita
    db/derby/docs/trunk/src/devguide/cdevstart18978.dita
    db/derby/docs/trunk/src/devguide/cdevstart19524.dita
    db/derby/docs/trunk/src/devguide/cdevstart39409.dita
    db/derby/docs/trunk/src/devguide/cdevstart41260.dita
    db/derby/docs/trunk/src/devguide/cdevstart813142.dita
    db/derby/docs/trunk/src/devguide/cdevstart813545.dita
    db/derby/docs/trunk/src/devguide/cdevstart98282.dita
    db/derby/docs/trunk/src/devguide/cdevtricks19707.dita
    db/derby/docs/trunk/src/devguide/cdevtricks21248.dita
    db/derby/docs/trunk/src/devguide/cdevtricks23426.dita
    db/derby/docs/trunk/src/devguide/cdevtricks807337.dita
    db/derby/docs/trunk/src/devguide/cdevtricks807400.dita
    db/derby/docs/trunk/src/devguide/cdevupgrades.dita
    db/derby/docs/trunk/src/devguide/rdevconcepts600.dita
    db/derby/docs/trunk/src/devguide/rdevconcepts713.dita
    db/derby/docs/trunk/src/devguide/rdevconcepts8424.dita
    db/derby/docs/trunk/src/devguide/rdevconceptsholdablecursors.dita
    db/derby/docs/trunk/src/devguide/rdevconceptssur.dita
    db/derby/docs/trunk/src/devguide/rdevcsecure125.dita
    db/derby/docs/trunk/src/devguide/rdevcsecure13713.dita
    db/derby/docs/trunk/src/devguide/rdevcsecure26537.dita
    db/derby/docs/trunk/src/devguide/rdevcsecure379.dita
    db/derby/docs/trunk/src/devguide/rdevcsecure557.dita
    db/derby/docs/trunk/src/devguide/rdevcsecure608.dita
    db/derby/docs/trunk/src/devguide/rdevcsecure766.dita
    db/derby/docs/trunk/src/devguide/rdevcsecure871406.dita
    db/derby/docs/trunk/src/devguide/rdevcsecure871422.dita
    db/derby/docs/trunk/src/devguide/rdevcsecure871439.dita
    db/derby/docs/trunk/src/devguide/rdevdeploy856948.dita
    db/derby/docs/trunk/src/devguide/rdevdvlp22102.dita
    db/derby/docs/trunk/src/devguide/rdevdvlp38881.dita
    db/derby/docs/trunk/src/devguide/rdevexudclass.dita
    db/derby/docs/trunk/src/devguide/rdevprocsqle.dita
    db/derby/docs/trunk/src/devguide/rdevresman79556.dita
    db/derby/docs/trunk/src/devguide/rdevtrademderby.dita
    db/derby/docs/trunk/src/devguide/tdevcsecure81850.dita
    db/derby/docs/trunk/src/devguide/tdevcsecure82556.dita
    db/derby/docs/trunk/src/devguide/tdevcsecurenewbootpw.dita
    db/derby/docs/trunk/src/devguide/tdevcsecurenewextkey.dita
    db/derby/docs/trunk/src/devguide/tdevcsecurenewkeyoverview.dita
    db/derby/docs/trunk/src/devguide/tdevcsecureunencrypteddb.dita
    db/derby/docs/trunk/src/devguide/tdevdeploy26887.dita
    db/derby/docs/trunk/src/devguide/tdevdeploy33704.dita
    db/derby/docs/trunk/src/devguide/tdevdeploy39856.dita
    db/derby/docs/trunk/src/devguide/tdevdvlp20349.dita
    db/derby/docs/trunk/src/devguide/tdevdvlp38381.dita
    db/derby/docs/trunk/src/devguide/tdevdvlp39090.dita
    db/derby/docs/trunk/src/devguide/tdevdvlp40140.dita
    db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita
    db/derby/docs/trunk/src/devguide/tdevpreupgrade.dita
    db/derby/docs/trunk/src/devguide/tdevupgradedb.dita
    db/derby/docs/trunk/src/devguide/tdevupgradesoft.dita

Modified: db/derby/docs/trunk/src/devguide/cdevadvjdbc18939.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevadvjdbc18939.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevadvjdbc18939.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevadvjdbc18939.dita Fri Mar 30 08:17:01 2007
@@ -35,7 +35,7 @@
 JVM remains active and available for further testing, and the database connection
 established during the test remains open.</p>
 <p>Because of the behaviors of the IDE described above, if you use the embedded <ph
-conref="devconrefs.dita#prod/productshortname"></ph> JDBC driver, you may
+conref="../conrefs.dita#prod/productshortname"></ph> JDBC driver, you may
 encounter errors connecting in the following situations:</p>
 <ul>
 <li>You test an individual query or database connection and then try to run

Modified: db/derby/docs/trunk/src/devguide/cdevadvjdbc32436.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevadvjdbc32436.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevadvjdbc32436.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevadvjdbc32436.dita Fri Mar 30 08:17:01 2007
@@ -21,8 +21,8 @@
 <concept id="cdevadvjdbc32436" xml:lang="en-us">
 <title>Using Derby with IDEs</title>
 <shortdesc>When you use an integrated development environment (IDE) to develop
-an embedded <ph conref="devconrefs.dita#prod/productshortname"></ph> application,
-you might need to run <ph conref="devconrefs.dita#prod/productshortname"></ph> within
+an embedded <ph conref="../conrefs.dita#prod/productshortname"></ph> application,
+you might need to run <ph conref="../conrefs.dita#prod/productshortname"></ph> within
 a server framework.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>IDEs<indexterm>using Derby with</indexterm><indexterm>and
@@ -30,14 +30,14 @@
 </metadata></prolog>
 <conbody>
 <p>This is because an IDE might try connecting to the database from two different
-JVMs, whereas only a single JVM instance should connect to a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+JVMs, whereas only a single JVM instance should connect to a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
 at one time (multiple connections from the same JVM are allowed). </p>
-<p>An "embedded <ph conref="devconrefs.dita#prod/productshortname"></ph> application"
+<p>An "embedded <ph conref="../conrefs.dita#prod/productshortname"></ph> application"
 is one which runs in the same JVM as the application. Such an application
-uses the embedded <ph conref="devconrefs.dita#prod/productshortname"></ph> driver
+uses the embedded <ph conref="../conrefs.dita#prod/productshortname"></ph> driver
 (<i>org.apache.derby.jdbc.EmbeddedDriver</i>) and connection URL (<codeph><i>jdbc:derby:databaseName</i></codeph>).
 If you use this driver name or connection URL from the IDE, when the IDE tries
-to open a second connection to the same database with the embedded <ph conref="devconrefs.dita#prod/productshortname"></ph>,
+to open a second connection to the same database with the embedded <ph conref="../conrefs.dita#prod/productshortname"></ph>,
 the attempt fails. Two JVMs cannot connect to the same database in embedded
 mode.</p>
 </conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevadvjdbc41138.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevadvjdbc41138.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevadvjdbc41138.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevadvjdbc41138.dita Fri Mar 30 08:17:01 2007
@@ -33,18 +33,18 @@
 <conbody>
 <p>If no more properties are necessary, the call returns an array of zero
 length.</p>
-<p>In a <ph conref="devconrefs.dita#prod/productshortname"></ph> system, do
+<p>In a <ph conref="../conrefs.dita#prod/productshortname"></ph> system, do
 not use the method against an instance of <i>org.apache.derby.jdbc.EmbeddedDriver</i>.
 Instead, request the JDBC driver from the driver manager:</p>
 <codeblock>java.sql.DriverManager.getDriver(
     "jdbc:derby:").getPropertyInfo(<i>URL</i>, <i>Prop</i>)</codeblock>
-<p>In a <ph conref="devconrefs.dita#prod/productshortname"></ph> system, the
+<p>In a <ph conref="../conrefs.dita#prod/productshortname"></ph> system, the
 properties returned in the <i>DriverPropertyInfo</i> object are connection
 URL attributes, including a list of booted databases in a system (the <codeph><i>databaseName</i></codeph> attribute).</p>
 <p>Databases in a system are not automatically booted until you connect with
 them. You can configure your system to retain the former behavior, in which
 case the steps described in this section will continue to work. See <i>"derby.system.bootAll" </i> in <cite><ph
-conref="devconrefs.dita#pub/cittuning"></ph></cite>.</p>
+conref="../conrefs.dita#pub/cittuning"></ph></cite>.</p>
 <p><i>getPropertyInfo</i> requires a connection URL and a <codeph><i>Properties</i></codeph> object
 as parameters. Typically, what you pass are values that you will use in a
 future call to <codeph><i>java.sql.DriverManager.getConnection</i></codeph> when

Modified: db/derby/docs/trunk/src/devguide/cdevbabejgjd.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevbabejgjd.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevbabejgjd.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevbabejgjd.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 <concept id="cdevbabejgjd" xml:lang="en-us">
 <title>Granting permissions to Derby</title>
 <shortdesc>This section discusses which permissions should be granted to <ph
-conref="devconrefs.dita#prod/productshortname"></ph> (the code base derby.jar).</shortdesc>
+conref="../conrefs.dita#prod/productshortname"></ph> (the code base derby.jar).</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Permissions<indexterm>granting to Derby</indexterm></indexterm>
 </keywords>
@@ -30,25 +30,25 @@
 ></synph> for more information about creating policy files.</p>
 <section><title>Mandatory permissions</title><dl><dlentry>
 <dt>permission java.lang.RuntimePermission createClassLoader</dt>
-<dd>Mandatory. It allows <ph conref="devconrefs.dita#prod/productshortname"></ph> to
+<dd>Mandatory. It allows <ph conref="../conrefs.dita#prod/productshortname"></ph> to
 execute SQL queries and supports loading class files from jar files stored
 in the database.</dd>
 </dlentry><dlentry>
 <dt>permission java.util.PropertyPermission "derby.*", read</dt>
-<dd>Allows <ph conref="devconrefs.dita#prod/productshortname"></ph> to read
-individual <ph conref="devconrefs.dita#prod/productshortname"></ph> properties
+<dd>Allows <ph conref="../conrefs.dita#prod/productshortname"></ph> to read
+individual <ph conref="../conrefs.dita#prod/productshortname"></ph> properties
 set in the JVM's system set. If the action is denied, properties in the JVM's
 system set are ignored.</dd>
 </dlentry></dl></section>
 <section><title>Database access permissions</title><dl><dlentry>
 <dt>permission java.io.FilePermission "directory${/}/-", "read,write,delete"</dt>
-<dd>Allows <ph conref="devconrefs.dita#prod/productshortname"></ph> to manage
+<dd>Allows <ph conref="../conrefs.dita#prod/productshortname"></ph> to manage
 files within the database that maps to the directory specified. For read-only
 databases, only the "read" action needs to be granted.</dd>
 </dlentry></dl></section>
 <section><title>Optional permissions</title><dl><dlentry>
 <dt>permission java.io.FilePermission "${derby.system.home}", "read,write"</dt>
-<dd>Allows <ph conref="devconrefs.dita#prod/productshortname"></ph> to determine
+<dd>Allows <ph conref="../conrefs.dita#prod/productshortname"></ph> to determine
 the system directory when set by d<i>b2j.system.home </i>and create it if
 needed. If the system directory already exists then only the "read" permission
 needs to be granted.</dd>
@@ -59,23 +59,23 @@
 </dlentry><dlentry>
 <dt>permission java.io.FilePermission "${derby.system.home}${/}derby.properties",
 "read"</dt>
-<dd>Allows <ph conref="devconrefs.dita#prod/productshortname"></ph> to read
+<dd>Allows <ph conref="../conrefs.dita#prod/productshortname"></ph> to read
 the system properties file from the system directory.</dd>
 </dlentry><dlentry>
 <dt>permission java.io.FilePermission "${derby.system.home}${/}derby.log",
 "read,write,delete"</dt>
 <dt>permission java.io.FilePermission "${user.dir}${/}derby.log", "read,write,delete"</dt>
 <dd>Only one of these permissions is needed. Permits the application to read,
-write, and delete to the <ph conref="devconrefs.dita#prod/productshortname"></ph> log
+write, and delete to the <ph conref="../conrefs.dita#prod/productshortname"></ph> log
 file, unless the log has been re-directed. (See the <i>derby.stream.error </i>properties
-in <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite> for more
-information.) If one of the requested valid actions is denied, the <ph conref="devconrefs.dita#prod/productshortname"></ph> log
+in <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite> for more
+information.) If one of the requested valid actions is denied, the <ph conref="../conrefs.dita#prod/productshortname"></ph> log
 will be <codeph><i>java.lang.System.err</i></codeph>.</dd>
 </dlentry></dl></section>
 <section><title>Combining permissions</title><p>You might grant one <i>FilePermission</i> that
 encompasses several or all of the permissions instead of separately granting
 a number of the more specific permissions. For example:<codeblock>permission java.io.FilePermission "${derby.system.home}/-", "read,write,delete"</codeblock
->This allows the <ph conref="devconrefs.dita#prod/productshortname"></ph> engine
+>This allows the <ph conref="../conrefs.dita#prod/productshortname"></ph> engine
 complete access to the system directory and any databases contained in the
 system directory.</p></section>
 </conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevcbabejdfj.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcbabejdfj.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcbabejdfj.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcbabejdfj.dita Fri Mar 30 08:17:01 2007
@@ -19,7 +19,7 @@
 <concept xml:lang="en-us" id="cdevcbabejdfj">
 <title>Running Derby under a security manager</title>
 <shortdesc>When running within an application or application server with a Java 2
-Security Manager enabled, <ph conref="devconrefs.dita#prod/productshortname"></ph> must be granted certain permissions
+Security Manager enabled, <ph conref="../conrefs.dita#prod/productshortname"></ph> must be granted certain permissions
 to execute and access database files.</shortdesc>
 <prolog><metadata>
 <keywords>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts10914.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts10914.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts10914.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts10914.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevconcepts10914" xml:lang="en-us">
 <title>Multi-user database access</title>
-<shortdesc>Multi-user database access is possible if <ph conref="devconrefs.dita#prod/productshortname"></ph> is
+<shortdesc>Multi-user database access is possible if <ph conref="../conrefs.dita#prod/productshortname"></ph> is
 running inside a server framework.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Multi-user database access<indexterm>programming for</indexterm></indexterm>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts14433.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts14433.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts14433.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts14433.dita Fri Mar 30 08:17:01 2007
@@ -22,7 +22,7 @@
 <title>Statement versus transaction runtime rollback</title>
 <shortdesc>When an SQL statement generates an exception, this exception results
 in a <i>runtime rollback</i>. A runtime rollback is a system-generated rollback
-of a statement or transaction by <ph conref="devconrefs.dita#prod/productshortname"></ph>,
+of a statement or transaction by <ph conref="../conrefs.dita#prod/productshortname"></ph>,
 as opposed to an explicit <codeph><i>rollback</i></codeph> call from your
 application.</shortdesc>
 <prolog><metadata>
@@ -32,15 +32,15 @@
 <conbody>
 <p>Extremely severe exceptions, such as disk-full errors, shut down the system,
 and the transaction is rolled back when the database is next booted. Severe
-exceptions, such as deadlock, cause transaction rollback; <ph conref="devconrefs.dita#prod/productshortname"></ph> rolls
+exceptions, such as deadlock, cause transaction rollback; <ph conref="../conrefs.dita#prod/productshortname"></ph> rolls
 back all changes since the beginning of the transaction and implicitly begins
 a new transaction. Less severe exceptions, such as syntax errors, result in
-statement rollback; <ph conref="devconrefs.dita#prod/productshortname"></ph> rolls
+statement rollback; <ph conref="../conrefs.dita#prod/productshortname"></ph> rolls
 back only changes made by the statement that caused the error. The application
 developer can insert code to explicitly roll back the entire transaction if
 desired.</p>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> supports partial
-rollback through the use of savepoints. See the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite> for
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> supports partial
+rollback through the use of savepoints. See the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite> for
 more information.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts15366.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts15366.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts15366.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts15366.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevconcepts15366" xml:lang="en-us">
 <title>Isolation levels and concurrency</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> provides
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> provides
 four transaction isolation levels. Setting the transaction isolation level
 for a connection allows a user to specify how severely the user's transaction
 should be isolated from other transactions.</shortdesc>
@@ -62,7 +62,7 @@
 names for isolation levels whether they are set through the JDBC method or
 an SQL statement.</p>
 <table frame="all" id="cdevconceptsiso_level"><title>Mapping of JDBC transaction
-isolation levels to <ph conref="devconrefs.dita#prod/productshortname"></ph> isolation
+isolation levels to <ph conref="../conrefs.dita#prod/productshortname"></ph> isolation
 levels</title>
 <tgroup cols="2" colsep="1" rowsep="1"><colspec colname="colspec0" colwidth="260*"/>
 <colspec colname="colspec1" colwidth="186*"/>
@@ -191,18 +191,18 @@
 <ul>
 <li><codeph>TRANSACTION_SERIALIZABLE</codeph> <p><codeph>RR</codeph>, <codeph>SERIALIZABLE</codeph>,
 or <codeph>REPEATABLE READ</codeph> from SQL.</p> <p><i>TRANSACTION_SERIALIZABLE</i> means
-that <ph conref="devconrefs.dita#prod/productshortname"></ph> treats the transactions
+that <ph conref="../conrefs.dita#prod/productshortname"></ph> treats the transactions
 as if they occurred serially (one after the other) instead of concurrently. <ph
-conref="devconrefs.dita#prod/productshortname"></ph> issues locks to prevent
+conref="../conrefs.dita#prod/productshortname"></ph> issues locks to prevent
 all the transaction anomalies listed in <xref href="cdevconcepts15366.dita#cdevconcepts15366/cdevconcepts17741"></xref> from
 occurring. The type of lock it issues is sometimes called a <i>range lock</i>.</p></li>
 <li><codeph>TRANSACTION_REPEATABLE_READ</codeph>   <p><codeph>RS</codeph> from
-SQL.</p> <p><i>TRANSACTION_REPEATABLE_READ</i> means that <ph conref="devconrefs.dita#prod/productshortname"></ph> issues
+SQL.</p> <p><i>TRANSACTION_REPEATABLE_READ</i> means that <ph conref="../conrefs.dita#prod/productshortname"></ph> issues
 locks to prevent only dirty reads and non-repeatable reads, but not phantoms.
 It does not issue range locks for selects.</p></li>
 <li><codeph>TRANSACTION_READ_COMMITTED</codeph>  <p><codeph>CS</codeph> or <codeph>CURSOR
 STABILITY</codeph> from SQL.</p> <p><i>TRANSACTION_READ_COMMITTED</i> means
-that <ph conref="devconrefs.dita#prod/productshortname"></ph> issues locks
+that <ph conref="../conrefs.dita#prod/productshortname"></ph> issues locks
 to prevent only dirty reads, not all the transaction anomalies listed in <xref
 href="#cdevconcepts15366/cdevconcepts17741"></xref>.</p> <p><i>TRANSACTION_READ_COMMITTED</i> is
 the default isolation level for transactions.</p></li>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts16400.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts16400.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts16400.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts16400.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
 <concept id="cdevconcepts16400" xml:lang="en-us">
 <title>Configuring deadlock detection and lock wait timeouts</title>
 <shortdesc>You configure the amount of time a transaction waits before <ph
-conref="devconrefs.dita#prod/productshortname"></ph> does any deadlock checking
+conref="../conrefs.dita#prod/productshortname"></ph> does any deadlock checking
 with the <i>derby.locks.deadlockTimeout</i> property.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>deadlocks<indexterm>configuring detection</indexterm></indexterm>
@@ -35,11 +35,11 @@
 example, in order for any deadlock checking to occur, the <codeph><i>derby.locks.deadlockTimeout</i></codeph> property
 must be set to a value lower than the <codeph><i>derby.locks.waitTimeout</i></codeph> property.
 If it is set to a value equal to or higher than the <codeph><i>derby.locks.waitTimeout</i></codeph>,
-the transaction times out before <ph conref="devconrefs.dita#prod/productshortname"></ph> does
+the transaction times out before <ph conref="../conrefs.dita#prod/productshortname"></ph> does
 any deadlock checking.</p>
 <p><indexterm>Deadlocks<indexterm>detecting</indexterm></indexterm>By default, <i>derby.locks.waitTimeout</i> is
 set to 60 seconds. -1 is the equivalent of no wait timeout. This means that
-transactions never time out, although <ph conref="devconrefs.dita#prod/productshortname"></ph> can
+transactions never time out, although <ph conref="../conrefs.dita#prod/productshortname"></ph> can
 choose a transaction as a deadlock victim.</p>
 <fig expanse="column" id="cdevconcepts27089"><title>One possible configuration:
 deadlock checking occurs when a transaction has waited 30 seconds; no lock

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts19173.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts19173.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts19173.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts19173.dita Fri Mar 30 08:17:01 2007
@@ -31,7 +31,7 @@
 <p>All the statements in the transaction are <i>atomic</i>. A transaction
 is associated with a single <codeph><i>Connection</i></codeph> object (and
 database). A transaction cannot span <i>Connections</i> (or databases).</p>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> permits schema
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> permits schema
 and data manipulation statements (DML) to be intermixed within a single transaction.
 If you create a table in one transaction, you can also insert into it in that
 same transaction. A schema manipulation statement (DDL) is not automatically

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts19524.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts19524.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts19524.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts19524.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevconcepts19524" xml:lang="en-us">
 <title>Controlling Derby application behavior</title>
-<shortdesc>This section looks at some advanced <ph conref="devconrefs.dita#prod/productshortname"></ph> application
+<shortdesc>This section looks at some advanced <ph conref="../conrefs.dita#prod/productshortname"></ph> application
 concepts.</shortdesc>
 <conbody></conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts22300.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts22300.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts22300.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts22300.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
 <concept id="cdevconcepts22300" xml:lang="en-us">
 <title>Configuring isolation levels</title>
 <shortdesc>If a connection does not specify its isolation level, it inherits
-the default isolation level for the <ph conref="devconrefs.dita#prod/productshortname"></ph> system.
+the default isolation level for the <ph conref="../conrefs.dita#prod/productshortname"></ph> system.
 The default value is <codeph>CS</codeph>.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Isolation levels<indexterm>configuring</indexterm></indexterm>
@@ -37,16 +37,16 @@
 <p>To override the inherited default, use the methods of <i>java.sql.Connection</i>.</p>
 <p>In addition, a connection can change the isolation level of the transaction
 within an SQL statement. For more information, see "SET ISOLATION statement"
-in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>. You can
+in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>. You can
 use the WITH clause to change the isolation level for the current statement
 only, not the transaction. For information about the WITH clause, see
-"SELECT statement" in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>. </p>
+"SELECT statement" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>. </p>
 <p> In all cases except when you change the isolation level using the WITH
 clause, changing the isolation level commits the current transaction. In most
 cases, the current transaction is committed even if you set the isolation level
 in a way that does not change it (that is, if you set it to its current value).
 See <xref href="cdevconcepts15366.dita#cdevconcepts15366"></xref> for details.</p>
 <note>For information about how to choose a particular isolation level, see <cite><ph
-conref="devconrefs.dita#pub/cittuning"></ph></cite>.</note>
+conref="../conrefs.dita#pub/cittuning"></ph></cite>.</note>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts22641.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts22641.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts22641.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts22641.dita Fri Mar 30 08:17:01 2007
@@ -22,7 +22,7 @@
 <title>Scrollable result sets</title>
 <shortdesc>JDBC 2.0 adds two new types of result sets which allows
 you to scroll in either direction or to move the cursor to a
-particular row. <ph conref="devconrefs.dita#prod/productshortname"></ph> supports one of
+particular row. <ph conref="../conrefs.dita#prod/productshortname"></ph> supports one of
 these types: scrollable insensitive result sets
 (<codeph>ResultSet.TYPE_SCROLL_INSENSITIVE</codeph>).
 </shortdesc>
@@ -34,7 +34,7 @@
 
 <p>When you use a result set of type of type
 <codeph>ResultSet.TYPE_SCROLL_INSENSITIVE</codeph>, <ph
-conref="devconrefs.dita#prod/productshortname"></ph> materializes rows
+conref="../conrefs.dita#prod/productshortname"></ph> materializes rows
 from the first one in the result set up to the one with the biggest
 row number as the rows are requested. The materialized rows will be
 backed to disk if necessary, to avoid excessive memory usage. 
@@ -43,7 +43,7 @@
 <p>
 Insensitive result sets, in contrast to sensitive result sets,
 are insensitive to changes made by others on the rows which have been
-materialized. <ph conref="devconrefs.dita#prod/productshortname"></ph>
+materialized. <ph conref="../conrefs.dita#prod/productshortname"></ph>
 allows updates of scrollable insensitive result sets, please see <xref
 href="rdevconceptssur.dita#visibility">Visibilty of changes</xref>,
 which also explains visibility of own changes.
@@ -51,7 +51,7 @@
 
 <p>
 <note>
-<ph conref="devconrefs.dita#prod/productshortname"></ph> does not
+<ph conref="../conrefs.dita#prod/productshortname"></ph> does not
 support result sets of type ResultSet.TYPE_SCROLL_SENSITIVE.
 </note>
 </p>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts23810.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts23810.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts23810.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts23810.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevconcepts23810" xml:lang="en-us">
 <title>Lock granularity</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> can be
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> can be
 configured for <i>table-level</i> locking. With table-level locking, when
 a transaction locks data in order to prevent any transaction anomalies, it
 always locks the entire table, not just those rows being accessed.</shortdesc>
@@ -29,20 +29,20 @@
 </keywords>
 </metadata></prolog>
 <conbody>
-<p>By default, <ph conref="devconrefs.dita#prod/productshortname"></ph> is
+<p>By default, <ph conref="../conrefs.dita#prod/productshortname"></ph> is
 configured for row-level locking. Row-level locking uses more memory but allows
 greater concurrency, which works better in multi-user systems. Table-level
 locking works best with single-user applications or read-only applications. </p>
-<p>You typically set lock granularity for the entire <ph conref="devconrefs.dita#prod/productshortname"></ph> system,
-not for a particular application. However, at runtime, <ph conref="devconrefs.dita#prod/productshortname"></ph> may
+<p>You typically set lock granularity for the entire <ph conref="../conrefs.dita#prod/productshortname"></ph> system,
+not for a particular application. However, at runtime, <ph conref="../conrefs.dita#prod/productshortname"></ph> may
 escalate the lock granularity for a particular transaction from row-level
 locking to table-level locking for performance reasons. You have some control
 over the threshold at which this occurs. For information on turning off row-level
-locking, see <i>"derby.storage.rowLocking" </i> in <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>.
+locking, see <i>"derby.storage.rowLocking" </i> in <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite>.
 For more information about automatic lock escalation, see "About the System's
 Selection of Lock Granularity" and "Transaction-Based Lock Escalation" in <cite><ph
-conref="devconrefs.dita#pub/cittuning"></ph></cite><cite>. </cite>For more
-information on tuning your <ph conref="devconrefs.dita#prod/productshortname"></ph> system,
+conref="../conrefs.dita#pub/cittuning"></ph></cite><cite>. </cite>For more
+information on tuning your <ph conref="../conrefs.dita#prod/productshortname"></ph> system,
 see "Tuning Databases and Applications".</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts24927.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts24927.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts24927.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts24927.dita Fri Mar 30 08:17:01 2007
@@ -25,7 +25,7 @@
 If your application runs on JDK 1.6 or higher, the exceptions
 will be the refined subtypes of <i>java.sql.SQLException</i>
 introduced by JDBC4.
-To see the exceptions generated by <ph conref="devconrefs.dita#prod/productshortname"></ph>,
+To see the exceptions generated by <ph conref="../conrefs.dita#prod/productshortname"></ph>,
 retrieve and process the <codeph><i>SQLExceptions</i></codeph> in a catch
 block.</shortdesc>
 <prolog><metadata>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts28351.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts28351.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts28351.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts28351.dita Fri Mar 30 08:17:01 2007
@@ -22,7 +22,7 @@
 <title>Updatable result sets</title>
 <shortdesc>
 Updatable result sets in <ph
-conref="devconrefs.dita#prod/productshortname"></ph> can be updated by
+conref="../conrefs.dita#prod/productshortname"></ph> can be updated by
 using result set update methods
 (<codeph>updateRow()</codeph>,<codeph>deleteRow()</codeph> and
 <codeph>insertRow()</codeph>), or by using positioned update or delete
@@ -33,11 +33,11 @@
 <section>
 
 <p> Both scrollable and non-scrollable result sets can be updatable in <ph
-conref="devconrefs.dita#prod/productshortname"></ph>. 
+conref="../conrefs.dita#prod/productshortname"></ph>. 
 </p>
 
 <p> If the query which was executed to create the result set is not updatable, 
-<ph conref="devconrefs.dita#prod/productshortname"></ph> will downgrade
+<ph conref="../conrefs.dita#prod/productshortname"></ph> will downgrade
 the concurrency mode to <codeph>ResultSet.CONCUR_READ_ONLY</codeph>,
 and add a warning about this on the <codeph>ResultSet</codeph>. The
 compilation of the query fails if the result set cannot be updatable,

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts29416.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts29416.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts29416.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts29416.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevconcepts29416" xml:lang="en-us">
 <title>Using auto-commit</title>
-<shortdesc>A new connection to a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<shortdesc>A new connection to a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
 is in auto-commit mode by default, as specified by the JDBC standard.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Auto-commit<indexterm>using</indexterm></indexterm></keywords>
@@ -33,7 +33,7 @@
 statement returning a <codeph><i>ResultSet</i></codeph>, the statement completes
 when the last row of the <codeph><i>ResultSet</i></codeph> has been retrieved
 or the <codeph><i>ResultSet</i></codeph> has been closed explicitly.</p>
-<p>Some applications might prefer to work with <ph conref="devconrefs.dita#prod/productshortname"></ph> in
+<p>Some applications might prefer to work with <ph conref="../conrefs.dita#prod/productshortname"></ph> in
 auto-commit mode; some might prefer to work with auto-commit turned off. You
 should be aware of the implications of using either model.</p>
 <p>You should be aware of the following when you use auto-commit:</p>
@@ -50,7 +50,7 @@
 <li><i>Database-side JDBC Procedures (procedures using nested connections)</i> 
  <p>You cannot execute procedures within SQL statements if those procedures
 perform a commit or rollback on the current connection. Since in the auto-commit
-mode all SQL statements are implicitly committed, <ph conref="devconrefs.dita#prod/productshortname"></ph> turns
+mode all SQL statements are implicitly committed, <ph conref="../conrefs.dita#prod/productshortname"></ph> turns
 off auto-commit during execution of database-side procedures and turns it
 back on when the method completes.</p><p>Procedures that use nested connections
 are not permitted to turn auto-commit on or off or to commit or roll back.</p></li>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts30291.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts30291.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts30291.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts30291.dita Fri Mar 30 08:17:01 2007
@@ -28,7 +28,7 @@
 </keywords>
 </metadata></prolog>
 <conbody>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> is configured
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> is configured
 by default to work well for multi-user systems. For single-user systems, you
 might want to tune your system so that it uses fewer resources; see <xref
 href="cdevconcepts23810.dita#cdevconcepts23810"></xref>.</p>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts30811.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts30811.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts30811.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts30811.dita Fri Mar 30 08:17:01 2007
@@ -28,6 +28,6 @@
 </metadata></prolog>
 <conbody>
 <p>For more information, see "SELECT statement" and "FOR UPDATE clause" in
-the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
+the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts34828.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts34828.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts34828.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts34828.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevconcepts34828" xml:lang="en-us">
 <title>Working with multiple connections to a single database</title>
-<shortdesc>This section discusses deploying <ph conref="devconrefs.dita#prod/productshortname"></ph> so
+<shortdesc>This section discusses deploying <ph conref="../conrefs.dita#prod/productshortname"></ph> so
 that many connections can exist to a single database.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Multiple connections<indexterm>in single application</indexterm></indexterm>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts36402.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts36402.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts36402.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts36402.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevconcepts36402" xml:lang="en-us">
 <title>Types and scope of locks in Derby systems</title>
-<shortdesc>There are several types of locks available in <ph conref="devconrefs.dita#prod/productshortname"></ph> systems,
+<shortdesc>There are several types of locks available in <ph conref="../conrefs.dita#prod/productshortname"></ph> systems,
 including exclusive, shared, and update locks.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Locks<indexterm>exclusive</indexterm><indexterm>shared</indexterm><indexterm>update</indexterm></indexterm>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts36881.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts36881.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts36881.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts36881.dita Fri Mar 30 08:17:01 2007
@@ -28,10 +28,10 @@
 </metadata></prolog>
 <conbody>
 <p>Within the scope of one <codeph><i>Connection</i></codeph>, you access
-only a single <ph conref="devconrefs.dita#prod/productshortname"></ph> database.
+only a single <ph conref="../conrefs.dita#prod/productshortname"></ph> database.
 (Database-side JDBC procedures can allow you to access more than one database
 in some circumstances.) A single application might allow one or more <codeph><i>Connections</i></codeph> to <ph
-conref="devconrefs.dita#prod/productshortname"></ph>, either to a single database
+conref="../conrefs.dita#prod/productshortname"></ph>, either to a single database
 or to many different databases, provided that all the databases are within
 the same system.</p>
 <p>With DriverManager, you use the connection URL as an argument to get the <codeph><i>getConnection</i></codeph> method

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts41275.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts41275.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts41275.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts41275.dita Fri Mar 30 08:17:01 2007
@@ -30,12 +30,12 @@
 </metadata></prolog>
 <conbody>
 <p>
-In <ph conref="devconrefs.dita#prod/productshortname"></ph>, any
+In <ph conref="../conrefs.dita#prod/productshortname"></ph>, any
 SELECT statement generates a cursor which can be controlled by a
 <codeph><i>java.sql.ResultSet</i></codeph> object. 
-<ph conref="devconrefs.dita#prod/productshortname"></ph> does not
+<ph conref="../conrefs.dita#prod/productshortname"></ph> does not
 support SQL-92's DECLARE CURSOR language construct to create cursors,
-however <ph conref="devconrefs.dita#prod/productshortname"></ph>
+however <ph conref="../conrefs.dita#prod/productshortname"></ph>
 supports positioned deletes and positioned updates of updatable
 cursors.
 </p>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita Fri Mar 30 08:17:01 2007
@@ -24,10 +24,10 @@
 particular application, you might need to do some debugging.</shortdesc>
 <prolog></prolog>
 <conbody>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> provides a class
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> provides a class
 to help you in this situation, <i>org.apache.derby.diag.LockTable</i>. You
 can also set the property <i>derby.locks.deadlockTrace</i> to dump additional
 information to the derby.log file about any deadlocks that occur on your system. 
-See the Tuning Guide for more information on this property. For information, see the <cite><ph conref="devconrefs.dita#pub/citadmin"></ph></cite>.</p>
+See the Tuning Guide for more information on this property. For information, see the <cite><ph conref="../conrefs.dita#pub/citadmin"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts53677.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts53677.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts53677.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts53677.dita Fri Mar 30 08:17:01 2007
@@ -22,11 +22,11 @@
 <title>Avoiding deadlocks</title>
 <shortdesc>Using both row-level locking and the TRANSACTION_READ_COMMITTED
 isolation level makes it likely that you will avoid deadlocks (both settings
-are <ph conref="devconrefs.dita#prod/productshortname"></ph> defaults). However,
+are <ph conref="../conrefs.dita#prod/productshortname"></ph> defaults). However,
 deadlocks are still possible.</shortdesc>
 <prolog></prolog>
 <conbody>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> application developers
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> application developers
 can avoid deadlocks by using consistent application logic; for example, transactions
 that access <i>Accounts</i> and <i>Orders</i> should always access the tables
 in the same order. That way, in the scenario described above, Transaction
@@ -36,6 +36,6 @@
 <p>Another tool available to you is the LOCK TABLE statement. A transaction
 can attempt to lock a table in exclusive mode when it starts to prevent other
 transactions from getting shared locks on a table. For more information, see
-"LOCK TABLE statement" in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
+"LOCK TABLE statement" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts65864.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts65864.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts65864.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts65864.dita Fri Mar 30 08:17:01 2007
@@ -34,6 +34,6 @@
 <p>In addition, some programmers might share a statement among multiple threads
 to avoid the overhead of each thread's having its own. Using the single statement
 cache, threads can share the same statement from <i>different connections</i>.
-For more information, see in <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>.</p>
+For more information, see in <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts839085.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts839085.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts839085.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts839085.dita Fri Mar 30 08:17:01 2007
@@ -26,7 +26,7 @@
 <keywords><indexterm>Explicit close of JDBC objects</indexterm></keywords>
 </metadata></prolog>
 <conbody>
-<p>Connections to <ph conref="devconrefs.dita#prod/productshortname"></ph> are
+<p>Connections to <ph conref="../conrefs.dita#prod/productshortname"></ph> are
 resources external to an application, and the garbage collector will not close
 them automatically. </p>
 <p>For example, close a <i>Statement</i> object using its <codeph><i>close</i></codeph> method;

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts840995.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts840995.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts840995.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts840995.dita Fri Mar 30 08:17:01 2007
@@ -34,7 +34,7 @@
 
 <p>If the result set has holdability 
 <codeph>ResultSet.CLOSE_CURSORS_AT_COMMIT</codeph>, combined with
-autocommit on, <ph conref="devconrefs.dita#prod/productshortname"></ph>
+autocommit on, <ph conref="../conrefs.dita#prod/productshortname"></ph>
 gives an exception on positioned updates and deletes because the
 cursor is closed immediately before the positioned statement is
 commenced, as mandated by JDBC. In contrast, no such implicit commit

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts844813.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts844813.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts844813.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts844813.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevconcepts844813" xml:lang="en-us">
 <title>Information provided in SQL Exceptions</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> provides
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> provides
 the message, <i>SQLState</i> values, and error codes in SQL exceptions.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>SQL warnings</indexterm><indexterm>SQL exceptions<indexterm>chaining</indexterm></indexterm>
@@ -30,10 +30,10 @@
 <p>Use the <codeph><i>getSQLState</i></codeph> and <codeph><i>getMessage</i></codeph> methods
 to view the <codeph><i>SQLState</i></codeph> and error messages. Use <codeph><i>getErrorCode</i></codeph> to
 see the error code. The error code defines the severity of the error and is
-not unique to each exception. <note>Severity is not standardized in <ph conref="devconrefs.dita#prod/productshortname"></ph>.
+not unique to each exception. <note>Severity is not standardized in <ph conref="../conrefs.dita#prod/productshortname"></ph>.
 Applications should not depend on the severity returned from SQL exceptions.</note></p>
 <p>Applications should also check for and process <i>java.sql.SQLWarnings</i>,
-which are processed in a similar way. <ph conref="devconrefs.dita#prod/productshortname"></ph> issues
+which are processed in a similar way. <ph conref="../conrefs.dita#prod/productshortname"></ph> issues
 an <codeph><i>SQLWarning</i></codeph> if the <codeph><i>create=true</i></codeph> attribute
 is specified and the database already exists.</p>
 </conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts95005.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts95005.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts95005.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts95005.dita Fri Mar 30 08:17:01 2007
@@ -21,23 +21,23 @@
 <concept id="cdevconcepts95005" xml:lang="en-us">
 <title>Deadlock detection</title>
 <shortdesc>When a transaction waits more than a specific amount of time to
-obtain a lock (called the deadlock timeout), <ph conref="devconrefs.dita#prod/productshortname"></ph> can
+obtain a lock (called the deadlock timeout), <ph conref="../conrefs.dita#prod/productshortname"></ph> can
 detect whether the transaction is involved in a deadlock.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Deadlock detection</indexterm></keywords>
 </metadata></prolog>
 <conbody>
-<p>When <ph conref="devconrefs.dita#prod/productshortname"></ph> analyzes
+<p>When <ph conref="../conrefs.dita#prod/productshortname"></ph> analyzes
 such a situation for deadlocks it tries to determine how many transactions
 are involved in the deadlock (two or more). Usually aborting one transaction
-breaks the deadlock. <ph conref="devconrefs.dita#prod/productshortname"></ph> must
+breaks the deadlock. <ph conref="../conrefs.dita#prod/productshortname"></ph> must
 pick one transaction as the victim and abort that transaction; it picks the
 transaction that holds the fewest number of locks as the victim, on the assumption
 that transaction has performed the least amount of work. (This may not be
 the case, however; the transaction might have recently been escalated from
 row-level locking to table locking and thus hold a small number of locks even
 though it has done the most work.) </p>
-<p>When <ph conref="devconrefs.dita#prod/productshortname"></ph> aborts the
+<p>When <ph conref="../conrefs.dita#prod/productshortname"></ph> aborts the
 victim transaction, it receives a deadlock error (an <i>SQLException</i> with
 an <codeph><i>SQLState</i></codeph> of 40001). The error message gives you
 the transaction IDs, the statements, and the status of locks involved in a
@@ -54,6 +54,6 @@
 href="cdevconcepts16400.dita#cdevconcepts16400"></xref>.</p>
 <note>Deadlocks are detected only within a single database. Deadlocks across
 multiple databases are not detected. Non-database deadlocks caused by Java
-synchronization primitives are not detected by <ph conref="devconrefs.dita#prod/productshortname"></ph>.</note>
+synchronization primitives are not detected by <ph conref="../conrefs.dita#prod/productshortname"></ph>.</note>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure10983.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure10983.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure10983.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure10983.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevcsecure10983" xml:lang="en-us">
 <title>Notes on the Derby security features</title>
-<shortdesc>The<ph conref="devconrefs.dita#prod/productshortname"></ph> security
+<shortdesc>The<ph conref="../conrefs.dita#prod/productshortname"></ph> security
 model has some basic limitations.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>security features<indexterm>limitations</indexterm></indexterm>
@@ -32,7 +32,7 @@
 also encrypted). Note, however, for a distributed/embedded system that a sophisticated
 user with the database encryption key might be able to physically change those
 properties in the database files.</p>
-<p>In addition, in the <ph conref="devconrefs.dita#prod/productshortname"></ph> system,
+<p>In addition, in the <ph conref="../conrefs.dita#prod/productshortname"></ph> system,
 it is not necessary to have a specific connection (or permission to access
 a particular database) to shut down the system. Any authenticated user can
 shut down the system.</p>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure12392.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure12392.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure12392.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure12392.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevcsecure12392" xml:lang="en-us">
 <title>Configuring security for your environment</title>
-<shortdesc>In most cases, you enable <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+<shortdesc>In most cases, you enable <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
 security features through the use of properties. It is important to understand
 the best way of setting properties for your environment.</shortdesc>
 <prolog><metadata>
@@ -28,15 +28,15 @@
 </keywords>
 </metadata></prolog>
 <conbody>
-<section><p><ph conref="devconrefs.dita#prod/productshortname"></ph> does
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> does
 not come with a built-in superuser. For that reason, be careful when configuring <ph
-conref="devconrefs.dita#prod/productshortname"></ph> for user authentication
+conref="../conrefs.dita#prod/productshortname"></ph> for user authentication
 and user authorization. </p><ol>
 <li>When first working with security, work with system-level properties only
 so that you can easily override them if you make a mistake. </li>
 <li>Be sure to create at least one valid user, and grant that user full (read-write)
 access. For example, you might always want to create a user called <i>sa</i> with
-the password <i><ph conref="devconrefs.dita#prod/productlowercase"></ph></i> while
+the password <i><ph conref="../conrefs.dita#prod/productlowercase"></ph></i> while
 you are developing. </li>
 <li>Test the authentication system while it is still configured at the system
 level. Be absolutely certain that you have configured the system correctly

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure21547.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure21547.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure21547.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure21547.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevcsecure21547" xml:lang="en-us">
 <title>Built-in Derby users</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> provides
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> provides
 a simple, built-in repository of user names and passwords.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>users<indexterm>built-in repository</indexterm></indexterm>
@@ -32,7 +32,7 @@
 Using built-in users is an alternative to using an external directory service
 such as LDAP.</p>
 <codeblock>derby.authentication.provider=BUILTIN</codeblock>
-<p>You can create user names and passwords for <ph conref="devconrefs.dita#prod/productshortname"></ph> users
+<p>You can create user names and passwords for <ph conref="../conrefs.dita#prod/productshortname"></ph> users
 by specifying them with the <i>derby.user.UserName</i> property.</p>
 <note>These user names are case-sensitive for user authentication. User names
 are <i>SQL92Identifiers</i>. Delimited identifiers are allowed:   <codeblock>derby.user."FRed"=java</codeblock></note>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure21561.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure21561.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure21561.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure21561.dita Fri Mar 30 08:17:01 2007
@@ -28,15 +28,15 @@
 </metadata></prolog>
 <conbody>
 <p>By writing your own class that fulfills some minimal requirements, you
-can hook <ph conref="devconrefs.dita#prod/productshortname"></ph> up to an <i>external
+can hook <ph conref="../conrefs.dita#prod/productshortname"></ph> up to an <i>external
 authentication service</i> other than LDAP. To do so, specify an external
 authentication service by setting the property <codeph><i>derby.authentication.provider</i></codeph> to
-a class name that you want <ph conref="devconrefs.dita#prod/productshortname"></ph> to
+a class name that you want <ph conref="../conrefs.dita#prod/productshortname"></ph> to
 load at startup.</p>
 <p>The class that provides the external authentication service must implement
 the public interface <i>org.apache.derby.authentication</i>.<i>UserAuthenticator</i> and
 throw exceptions of the type <i>java.sql.SQLException</i> where appropriate.</p>
-<p>Using a user-defined class makes <ph conref="devconrefs.dita#prod/productshortname"></ph> adaptable
+<p>Using a user-defined class makes <ph conref="../conrefs.dita#prod/productshortname"></ph> adaptable
 to various naming and directory services.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure24366.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure24366.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure24366.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure24366.dita Fri Mar 30 08:17:01 2007
@@ -19,7 +19,7 @@
 -->
 <concept id="cdevcsecure24366" xml:lang="en-us">
 <title>Encrypting databases on disk</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> provides
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> provides
 a way for you to encrypt your data on disk.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Database encryption</indexterm><indexterm>Databases<indexterm>encrypting</indexterm></indexterm>
@@ -32,7 +32,7 @@
 by a system administrator. In addition, the recipient of the data is trusted
 and should be capable of protecting the data. The only risk comes when transporting
 data over the wire, and data encryption happens during network transport only.</p>
-<p>However, <ph conref="devconrefs.dita#prod/productshortname"></ph> databases
+<p>However, <ph conref="../conrefs.dita#prod/productshortname"></ph> databases
 are platform-independent files that are designed to be easily shared in a
 number of ways, including transport over the Internet. Recipients of the data
 might not know how, or might not have the means, to properly protect the data.</p>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure24458.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure24458.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure24458.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure24458.dita Fri Mar 30 08:17:01 2007
@@ -36,7 +36,7 @@
 external user authorization service is case-sensitive, so Fred must always
 type his name that way.   <codeblock>Connection conn = DriverManager.getConnection(
     "jdbc:derby:myDB", "FRed", "flintstone");</codeblock></li>
-<li>Within the <ph conref="devconrefs.dita#prod/productshortname"></ph> user
+<li>Within the <ph conref="../conrefs.dita#prod/productshortname"></ph> user
 authorization system, Fred becomes a case-insensitive authorization identifier.
 Fred is known as <i>FRED</i>.</li>
 <li>When specifying which users are authorized to access the accounting database,
@@ -49,11 +49,11 @@
 <ul>
 <li>Within the user authentication system, Fred is known as <i>Fred!</i>.
 You must now put double quotes around the name, because it is not a valid <codeph><i>SQL92Identifier</i></codeph>.
-(<ph conref="devconrefs.dita#prod/productshortname"></ph> knows to remove
+(<ph conref="../conrefs.dita#prod/productshortname"></ph> knows to remove
 the double quotes when passing the name to the external authentication system.)
   <codeblock>Connection conn = DriverManager.getConnection(
     "jdbc:derby:myDB", "\"Fred!\"", "flintstone");</codeblock></li>
-<li>Within the <ph conref="devconrefs.dita#prod/productshortname"></ph> user
+<li>Within the <ph conref="../conrefs.dita#prod/productshortname"></ph> user
 authorization system, <i>Fred</i> becomes a case-sensitive authorization identifier.
 Fred is known as <i>Fred!</i>.</li>
 <li>When specifying which users are authorized to access the accounting database,
@@ -61,10 +61,10 @@
 always delimit with double quotation marks).   <codeblock>derby.fullAccessUsers=sa,"Fred!",manager</codeblock></li>
 </ul>
 <p>As shown in the first example, your external authentication system may
-be case-sensitive, whereas the authorization identifier within <ph conref="devconrefs.dita#prod/productshortname"></ph> may
+be case-sensitive, whereas the authorization identifier within <ph conref="../conrefs.dita#prod/productshortname"></ph> may
 not be. If your authentication system allows two distinct users whose names
 differ by case, delimit all user names within the connection request to make
-all user names case-sensitive within the <ph conref="devconrefs.dita#prod/productshortname"></ph> system.
+all user names case-sensitive within the <ph conref="../conrefs.dita#prod/productshortname"></ph> system.
 In addition, you must also delimit user names that do not conform to <i>SQL92Identifier</i> rules
 with double quotes.</p>
 </conbody>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure36127.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure36127.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure36127.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure36127.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
 <concept id="cdevcsecure36127" xml:lang="en-us">
 <title>Enabling user authentication</title>
 <shortdesc>To enable user authentication, set the <i>derby.connection.requireAuthentication</i> property
-to true. Otherwise, <ph conref="devconrefs.dita#prod/productshortname"></ph> does
+to true. Otherwise, <ph conref="../conrefs.dita#prod/productshortname"></ph> does
 not require a user name and password. You can set this property as a system-wide
 property or as a database-wide property.</shortdesc>
 <prolog><metadata>
@@ -32,9 +32,9 @@
 <p>For a multi-user product, you would typically set it for the system in
 the <i>derby.properties</i> file for your server, since it is in a trusted
 environment.</p>
-<note>If you start a <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<note>If you start a <ph conref="../conrefs.dita#prod/productshortname"></ph> system
 with user authentication enabled but without defining at least one user, you
-will not be able to shut down the system gracefully. When <ph conref="devconrefs.dita#prod/productshortname"></ph> is
+will not be able to shut down the system gracefully. When <ph conref="../conrefs.dita#prod/productshortname"></ph> is
 running in a connectivity server and user authentication is turned on, stopping
 the server requires a user name and password. You will need to alter shutdown
 scripts accordingly. </note>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure36595.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure36595.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure36595.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure36595.dita Fri Mar 30 08:17:01 2007
@@ -19,7 +19,7 @@
 -->
 <concept id="cdevcsecure36595" xml:lang="en-us">
 <title>User authorizations</title>
-<shortdesc>When you specify user authorizations, <ph conref="devconrefs.dita#prod/productshortname"></ph> verifies
+<shortdesc>When you specify user authorizations, <ph conref="../conrefs.dita#prod/productshortname"></ph> verifies
 that a user has been granted permission to access a system, database, object,
 or SQL action. </shortdesc>
 <prolog><metadata>
@@ -34,11 +34,11 @@
 properties</indexterm></indexterm></keywords>
 </metadata></prolog>
 <conbody>
-<p>There are two types of user authorization in <ph conref="devconrefs.dita#prod/productshortname"></ph>,
+<p>There are two types of user authorization in <ph conref="../conrefs.dita#prod/productshortname"></ph>,
 connection authorization and SQL authorization. <term>Connection authorization</term> specifies
 the access that users have to connect to a system or database. <term>SQL authorization</term> controls
 the permissions that users have on database objects or for SQL actions. You
-can set the user authorization properties in <ph conref="devconrefs.dita#prod/productshortname"></ph> as
+can set the user authorization properties in <ph conref="../conrefs.dita#prod/productshortname"></ph> as
 system-level properties or database-level properties.</p>
 <p>Set system-level user authorizations when you are developing applications,
 or when you want to specify a secure default authorization for all users to

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure37241.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure37241.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure37241.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure37241.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevcsecure37241" xml:lang="en-us">
 <title>Users and authorization identifiers</title>
-<shortdesc>User names within the <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<shortdesc>User names within the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
 are known as <i>authorization identifiers</i>. The authorization identifier
 is a string that represents the name of the user, if one was provided in the
 connection request.</shortdesc>
@@ -30,13 +30,13 @@
 <conbody>
 <p>For example, the built-in function CURRENT_USER returns the authorization
 identifier for the current user.</p>
-<p>Once the authorization identifier is passed to the <ph conref="devconrefs.dita#prod/productshortname"></ph> system,
+<p>Once the authorization identifier is passed to the <ph conref="../conrefs.dita#prod/productshortname"></ph> system,
 it becomes an <i>SQL92Identifier</i>. <codeph><i>SQL92Identifiers</i></codeph>-the
 kind of identifiers that represent database objects such as tables and columns-are
 case-insensitive (they are converted to all caps) unless delimited with double
 quotes, are limited to 128 characters, and have other limitations.</p>
 <p>User names must be valid authorization identifiers even if user authentication
 is turned off, and even if all users are allowed access to all databases.</p>
-<p>For more information about <i>SQL92Identifiers</i>, see the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
+<p>For more information about <i>SQL92Identifiers</i>, see the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure37817.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure37817.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure37817.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure37817.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
 -->
 <concept id="cdevcsecure37817" xml:lang="en-us">
 <title>Defining users</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> provides
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> provides
 several ways to define the repository of users and passwords. To specify which
-of these services to use with your <ph conref="devconrefs.dita#prod/productshortname"></ph> system,
+of these services to use with your <ph conref="../conrefs.dita#prod/productshortname"></ph> system,
 set the property <i>derby.authentication.provider</i> to the appropriate value
 as discussed here.</shortdesc>
 <prolog><metadata>
@@ -41,7 +41,7 @@
 <li><xref href="cdevcsecure21561.dita#cdevcsecure21561"></xref></li>
 <li><xref href="cdevcsecure21547.dita#cdevcsecure21547"></xref></li>
 </ul>
-<note>Shutting down the <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<note>Shutting down the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
 (for example, using the <i>shutdown=true</i> form of the connection URL without
 specifying a particular database) when user authentication is turned on requires
 that you define at least one user as a system-wide user.</note>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure38522.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure38522.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure38522.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure38522.dita Fri Mar 30 08:17:01 2007
@@ -22,7 +22,7 @@
 <title>External directory service</title>
 <shortdesc>A directory service stores names and attributes of those names.
 A typical use for a directory service is to store user names and passwords
-for a computer system. <ph conref="devconrefs.dita#prod/productshortname"></ph> uses
+for a computer system. <ph conref="../conrefs.dita#prod/productshortname"></ph> uses
 the Java naming and directory interface (JNDI) to interact with external directory
 services that can provide authentication of users' names and passwords.</shortdesc>
 <prolog><metadata>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure41285.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure41285.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure41285.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure41285.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
 -->
 <concept id="cdevcsecure41285" xml:lang="en-us">
 <title>LDAP directory service</title>
-<shortdesc>You can allow <ph conref="devconrefs.dita#prod/productshortname"></ph> to
+<shortdesc>You can allow <ph conref="../conrefs.dita#prod/productshortname"></ph> to
 authenticate users against an existing LDAP directory service within your
 enterprise. LDAP (lightweight directory access protocol) provides an open
 directory access protocol running over TCP/IP. An LDAP directory service can
@@ -37,7 +37,7 @@
 server. In addition, the Netscape Directory Synchronization Service synchronizes
 entries in a Windows NT directory with the entries in Netscape's Directory
 Server. It allows you to use the Windows NT directory as a repository for <ph
-conref="devconrefs.dita#prod/productshortname"></ph> users.</p></li>
+conref="../conrefs.dita#prod/productshortname"></ph> users.</p></li>
 <li>UMich slapd (freeware for the UNIX platform from the University of Michigan)</li>
 <li>AE SLAPD for Windows NT, from AEInc</li>
 </ul>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure42374.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure42374.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure42374.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure42374.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
 -->
 <concept id="cdevcsecure42374" xml:lang="en-us">
 <title>Working with user authentication</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> provides
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> provides
 support for user authentication. <term>User authentication</term> means that <ph
-conref="devconrefs.dita#prod/productshortname"></ph> authenticates the name
+conref="../conrefs.dita#prod/productshortname"></ph> authenticates the name
 and password for a user before allowing that user access to the system.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>user authentication<indexterm>overview</indexterm></indexterm>
@@ -32,42 +32,42 @@
 <conbody>
 <p>When user authentication is enabled (which it is not by default), the user
 requesting a connection must provide a valid name and password, which <ph
-conref="devconrefs.dita#prod/productshortname"></ph> verifies against the
-repository of users defined for the system. After <ph conref="devconrefs.dita#prod/productshortname"></ph> authenticates
-the user, it grants the user access to the <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+conref="../conrefs.dita#prod/productshortname"></ph> verifies against the
+repository of users defined for the system. After <ph conref="../conrefs.dita#prod/productshortname"></ph> authenticates
+the user, it grants the user access to the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
 but not necessarily access to the database made in the connection request.
-In the <ph conref="devconrefs.dita#prod/productshortname"></ph> system, access
+In the <ph conref="../conrefs.dita#prod/productshortname"></ph> system, access
 to a database is determined by <xref href="cdevcsecure36595.dita#cdevcsecure36595">user
 authorization</xref>.</p>
-<p>For user authentication, <ph conref="devconrefs.dita#prod/productshortname"></ph> allows
+<p>For user authentication, <ph conref="../conrefs.dita#prod/productshortname"></ph> allows
 you to provide a repository of users in a number of different ways. For example,
-you can hook <ph conref="devconrefs.dita#prod/productshortname"></ph> up to
+you can hook <ph conref="../conrefs.dita#prod/productshortname"></ph> up to
 an external directory service elsewhere in your enterprise, create your own
-directory service, or use <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+directory service, or use <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
 simple mechanism for creating a built-in repository of users.</p>
 <p>You can define a repository of users for a particular database or for an
 entire system, depending on whether you use system-wide or database-wide properties.</p>
-<p>When <ph conref="devconrefs.dita#prod/productshortname"></ph> user authentication
-is enabled and <ph conref="devconrefs.dita#prod/productshortname"></ph> uses
+<p>When <ph conref="../conrefs.dita#prod/productshortname"></ph> user authentication
+is enabled and <ph conref="../conrefs.dita#prod/productshortname"></ph> uses
 an external directory service, the architecture looks something like that
 shown in the figure below. </p>
-<fig expanse="column" id="cdevcsecure32704"><title><ph conref="devconrefs.dita#prod/productshortname"></ph> user
+<fig expanse="column" id="cdevcsecure32704"><title><ph conref="../conrefs.dita#prod/productshortname"></ph> user
 authentication using an external service. The application can be a single-user
-application with an embedded <ph conref="devconrefs.dita#prod/productshortname"></ph> engine
+application with an embedded <ph conref="../conrefs.dita#prod/productshortname"></ph> engine
 or a multi-user application server.</title>
 <image href="authentic_os.gif" placement="break"><alt>This figure shows Derby
 handling user authentication using an external service. </alt></image>
 </fig>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> always runs embedded
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> always runs embedded
 in another Java application, whether that application is a single-user application
 or a multiple-user application server or connectivity framework. </p>
 <p>A database can be accessed by only one JVM at a time, so it is possible
-to deploy a system in which the application in which <ph conref="devconrefs.dita#prod/productshortname"></ph> is
-embedded, not <ph conref="devconrefs.dita#prod/productshortname"></ph>, handles
+to deploy a system in which the application in which <ph conref="../conrefs.dita#prod/productshortname"></ph> is
+embedded, not <ph conref="../conrefs.dita#prod/productshortname"></ph>, handles
 the user authentication by connecting to an external directory service. </p>
 <fig expanse="column"><title>The application provides the user authentication
 using an external service. The application can be a single-user application
-with an embedded <ph conref="devconrefs.dita#prod/productshortname"></ph> engine
+with an embedded <ph conref="../conrefs.dita#prod/productshortname"></ph> engine
 or a multi-user application server.</title>
 <image href="appauth_os.gif" placement="break"><alt>This figure shows the
 application handling user authentication using an external service. </alt>

Modified: db/derby/docs/trunk/src/devguide/cdevcsecure51876.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure51876.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure51876.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure51876.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
 <concept id="cdevcsecure51876" xml:lang="en-us">
 <title>User authentication and authorization examples</title>
 <shortdesc>This section provides examples on using user authentication and
-authorization in <ph conref="devconrefs.dita#prod/productshortname"></ph> in
+authorization in <ph conref="../conrefs.dita#prod/productshortname"></ph> in
 either a client/server environment or in an embedded environment.</shortdesc>
 <prolog></prolog>
 <conbody></conbody>



Mime
View raw message