You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by sc...@apache.org on 2007/03/30 17:17:11 UTC
svn commit: r524118 [2/4] - /db/derby/docs/trunk/src/devguide/
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure60146.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure60146.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure60146.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure60146.dita Fri Mar 30 08:17:01 2007
@@ -30,7 +30,7 @@
<conbody>
<p>Encrypted databases cannot be booted automatically along with all other
system databases on system startup (see <i>"derby.system.bootAll" </i> in <cite><ph
-conref="devconrefs.dita#pub/cittuning"></ph></cite>). Instead, you boot encrypted
+conref="../conrefs.dita#pub/cittuning"></ph></cite>). Instead, you boot encrypted
databases when you first connect to the database.</p>
<p><dl><dlentry>
<dt>Booting a database with the <i>bootPassword</i> attribute</dt>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure67151.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure67151.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure67151.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure67151.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevcsecure67151" xml:lang="en-us">
<title>Specifying an alternate encryption algorithm</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> supports
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
the following encryption algorithms.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Encryption algorithms<indexterm>configuring</indexterm></indexterm>
@@ -50,11 +50,11 @@
<li>ECB</li>
<li>OFB</li>
</ul>
-<p>By default, <ph conref="devconrefs.dita#prod/productshortname"></ph> uses
+<p>By default, <ph conref="../conrefs.dita#prod/productshortname"></ph> uses
the DES algorithm of <i>DES/CBC/NoPadding</i>.</p>
<p>Specify an alternate encryption algorithm when you create a database with
the <i>encryptionAlgorithm=algorithm</i> attribute. If the algorithm you specify
-is not supported by the provider you have specified, <ph conref="devconrefs.dita#prod/productshortname"></ph> throws
+is not supported by the provider you have specified, <ph conref="../conrefs.dita#prod/productshortname"></ph> throws
an exception.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure79358.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure79358.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure79358.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure79358.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
<concept id="cdevcsecure79358" xml:lang="en-us">
<title>Programming applications for Derby user authentication</title>
<shortdesc>This section discusses programming user authentication into applications
-for use with <ph conref="devconrefs.dita#prod/productshortname"></ph>.</shortdesc>
+for use with <ph conref="../conrefs.dita#prod/productshortname"></ph>.</shortdesc>
<prolog><metadata>
<keywords><indexterm>User authentication<indexterm>programming applications
for</indexterm></indexterm></keywords>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure863546.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure863546.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure863546.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure863546.dita Fri Mar 30 08:17:01 2007
@@ -21,8 +21,8 @@
<concept id="cdevcsecure863546" xml:lang="en-us">
<title>LDAP performance issues</title>
<shortdesc>For performance reasons, the LDAP directory server should be in
-the same LAN as <ph conref="devconrefs.dita#prod/productshortname"></ph>. <ph
-conref="devconrefs.dita#prod/productshortname"></ph> does not cache the user's
+the same LAN as <ph conref="../conrefs.dita#prod/productshortname"></ph>. <ph
+conref="../conrefs.dita#prod/productshortname"></ph> does not cache the user's
credential information locally and thus must connect to the directory server
every time a user connects.</shortdesc>
<prolog></prolog>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure863676.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure863676.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure863676.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure863676.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevcsecure863676" xml:lang="en-us">
<title>LDAP restrictions</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> does not
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> does not
support LDAP groups.</shortdesc>
<prolog></prolog>
<conbody></conbody>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure864242.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure864242.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure864242.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure864242.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
-->
<concept id="cdevcsecure864242" xml:lang="en-us">
<title>JNDI-specific properties for external directory services</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> allows
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> allows
you to set a few advanced JNDI properties, which you can set in any of the
-supported ways of setting <ph conref="devconrefs.dita#prod/productshortname"></ph> properties.
+supported ways of setting <ph conref="../conrefs.dita#prod/productshortname"></ph> properties.
Typically you would set these at the same level (database or system) for which
you configured the external authentication service.</shortdesc>
<prolog><metadata>
@@ -36,7 +36,7 @@
Environment in the Java Naming and Directory API at <synph><var>http://java.sun.com/products/jndi/reference/api/index.html</var></synph>.
The external directory service must support the property.</p>
<p>Each JNDI provider has its set of properties that you can set within the <ph
-conref="devconrefs.dita#prod/productshortname"></ph> system.</p>
+conref="../conrefs.dita#prod/productshortname"></ph> system.</p>
<p>For example, you can set the property <i>java.naming.security.authentication</i> to
allow user credentials to be encrypted on the network if the provider supports
it. You can also specify that SSL be used with LDAP (LDAPS).</p>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure864642.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure864642.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure864642.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure864642.dita Fri Mar 30 08:17:01 2007
@@ -26,9 +26,9 @@
<conbody>
<p>You set the property once for each user. To delete a user, set that user's
password to null.</p>
-<codeblock><b>-- adding the user sa with password '<ph conref="devconrefs.dita#prod/productlowercase"></ph>pass'</b>
+<codeblock><b>-- adding the user sa with password '<ph conref="../conrefs.dita#prod/productlowercase"></ph>pass'</b>
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
- 'derby.user.sa', '<ph conref="devconrefs.dita#prod/productlowercase"></ph>pass')
+ 'derby.user.sa', '<ph conref="../conrefs.dita#prod/productlowercase"></ph>pass')
<b>-- adding the user mary with password 'little7xylamb'</b>
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.user.mary', 'little7xylamb')
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure864692.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure864692.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure864692.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure864692.dita Fri Mar 30 08:17:01 2007
@@ -27,11 +27,11 @@
<p>You set the value of this system-wide property once for each user, so you
can set it several times. To delete a user, remove that user from the file.</p>
<p>You can define this property in the usual ways- typically in the <i>derby.properties</i> file.
-For more information about setting properties, see <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>.</p>
+For more information about setting properties, see <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite>.</p>
<p>Here is a sample excerpt from the <i>derby.properties</i> file:</p>
<codeblock><b># Users definition
#</b>
-derby.user.sa=<ph conref="devconrefs.dita#prod/productlowercase"></ph>pass
+derby.user.sa=<ph conref="../conrefs.dita#prod/productlowercase"></ph>pass
derby.user.mary=little7xylamb</codeblock>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure865580.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure865580.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure865580.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure865580.dita Fri Mar 30 08:17:01 2007
@@ -24,6 +24,6 @@
<prolog></prolog>
<conbody>
<p>For information about user names and schemas, see "SET SCHEMA statement"
-in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite><cite>.</cite></p>
+in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite><cite>.</cite></p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure866716.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure866716.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure866716.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure866716.dita Fri Mar 30 08:17:01 2007
@@ -34,7 +34,7 @@
<note>The boot password should have at least as many characters as number
of bytes in the encryption key (56 bits=8 bytes, 168 bits=24 bytes, 128 bits=16
bytes). The minimum number of characters for the boot password allowed by <ph
-conref="devconrefs.dita#prod/productshortname"></ph> is eight.</note>
+conref="../conrefs.dita#prod/productshortname"></ph> is eight.</note>
<p>It is a good idea not to use words that would be easily guessed, such as
a login name or simple words or numbers. A <i>bootPassword</i>, like any password,
should be a mix of numbers and upper- and lowercase letters.</p>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure876908.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure876908.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure876908.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure876908.dita Fri Mar 30 08:17:01 2007
@@ -38,21 +38,21 @@
of names and attributes. This means that the user must provide a very long
name.</p>
<p>Typically, the user knows only a simple user name (e.g., the first part
-of the DN above, <i>mary</i>). With <ph conref="devconrefs.dita#prod/productshortname"></ph>,
-you do not need the full DN, because an LDAP client (<ph conref="devconrefs.dita#prod/productshortname"></ph>)
+of the DN above, <i>mary</i>). With <ph conref="../conrefs.dita#prod/productshortname"></ph>,
+you do not need the full DN, because an LDAP client (<ph conref="../conrefs.dita#prod/productshortname"></ph>)
can go to the directory first as a guest or even an anonymous user, search
for the full DN, then rebind to the directory using the full DN (and thus
authenticate the user).</p>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> typically initiates
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> typically initiates
a search for a full DN before binding to the directory using the full DN for
-user authentication. <ph conref="devconrefs.dita#prod/productshortname"></ph> does
+user authentication. <ph conref="../conrefs.dita#prod/productshortname"></ph> does
not initiate a search in the following cases:</p>
<ul>
<li>You have set <i>derby.authentication.ldap.searchFilter</i> to <i>derby.user</i>.</li>
<li>A user DN has been cached locally for the specific user with the <i>derby.user.UserName</i> property.</li>
</ul>
<p>For more information, see <i>derby.authentication.ldap.searchFilter</i> in <cite><ph
-conref="devconrefs.dita#pub/cittuning"></ph></cite>.</p>
+conref="../conrefs.dita#pub/cittuning"></ph></cite>.</p>
<p>Some systems permit anonymous searches; other require a user DN and password.
You can specify a user's DN and password for the search with the properties
listed below. In addition, you can limit the scope of the search by specifying
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure88690.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure88690.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure88690.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure88690.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevcsecure88690" xml:lang="en-us">
<title>Encrypting databases on creation</title>
-<shortdesc>You configure a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<shortdesc>You configure a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
for encryption when you create the database by specifying the <i>dataEncryption=true</i> attribute
on the connection URL.</shortdesc>
<prolog><metadata>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure90988.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure90988.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure90988.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure90988.dita Fri Mar 30 08:17:01 2007
@@ -20,24 +20,24 @@
-->
<concept id="cdevcsecure90988" xml:lang="en-us">
<title>Signed jar files</title>
-<shortdesc>In a Java 2 environment, <ph conref="devconrefs.dita#prod/productshortname"></ph> can
+<shortdesc>In a Java 2 environment, <ph conref="../conrefs.dita#prod/productshortname"></ph> can
detect digital signatures on jar files. When attempting to load a class from
-a signed jar file stored in the database, <ph conref="devconrefs.dita#prod/productshortname"></ph> will
+a signed jar file stored in the database, <ph conref="../conrefs.dita#prod/productshortname"></ph> will
verify the validity of the signature.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Jar files<indexterm>loading signed</indexterm></indexterm>
<indexterm>Signed jar files</indexterm></keywords>
</metadata></prolog>
<conbody>
-<note>The <ph conref="devconrefs.dita#prod/productshortname"></ph> class loader
+<note>The <ph conref="../conrefs.dita#prod/productshortname"></ph> class loader
only validates the integrity of the signed jar file and that the certificate
-has not expired. <ph conref="devconrefs.dita#prod/productshortname"></ph> cannot
+has not expired. <ph conref="../conrefs.dita#prod/productshortname"></ph> cannot
ascertain whether the validity/identity of declared signer is correct. To
validate identity, use a Security Manager (i.e., an implementation of <i>java.lang.SecurityManager</i>).</note>
<p>When loading classes from an application jar file in a Java 2 environment, <ph
-conref="devconrefs.dita#prod/productshortname"></ph> behaves as follows: </p>
+conref="../conrefs.dita#prod/productshortname"></ph> behaves as follows: </p>
<ul>
-<li><i>If the class is signed, <ph conref="devconrefs.dita#prod/productshortname"></ph> will:</i>
+<li><i>If the class is signed, <ph conref="../conrefs.dita#prod/productshortname"></ph> will:</i>
<ul>
<li>Verify that the jar was signed using a X.509 certificate (i.e., can be
represented by the class <i>java.security.cert.X509Certificate</i>). If not,
@@ -53,7 +53,7 @@
Key Infrastructure (PKI). </li>
</ul></li>
</ul>
-<note><ph conref="devconrefs.dita#prod/productshortname"></ph> does not provide
+<note><ph conref="../conrefs.dita#prod/productshortname"></ph> does not provide
a security manager.</note>
<p>For more information about signed jar files, see the Java 2 specifications
at <synph><var>http://java.sun.com</var></synph>.</p>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure96815.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure96815.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure96815.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure96815.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevcsecure96815" xml:lang="en-us">
<title>Requirements for Derby encryption</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> supports
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
disk encryption, but you must supply the following items.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Encryption<indexterm>providers</indexterm></indexterm>
@@ -29,7 +29,7 @@
<conbody>
<ul>
<li>An implementation of the Java Cryptographic Extension (JCE) package version
-1.2.1 or higher. <p><ph conref="devconrefs.dita#prod/productshortname"></ph> does
+1.2.1 or higher. <p><ph conref="../conrefs.dita#prod/productshortname"></ph> does
not support earlier, non-exportable, versions of JCE (such as JCE 1.2). More
information on JCE 1.2.1, including a product download, can be found at: <synph><var>http://java.sun.com/products/jce/index.html</var></synph>. </p
> <p>Any attempt to create or access an encrypted database without the libraries
@@ -37,7 +37,7 @@
Standard Edition, v 1.2 (J2SE) or higher, raises an exception; you will not
be able to create or boot the database.</p> <note>The JCE installation documentation
describes configuring (registering) the JCE software. You do not need to do
-this; <ph conref="devconrefs.dita#prod/productshortname"></ph> registers JCE
+this; <ph conref="../conrefs.dita#prod/productshortname"></ph> registers JCE
dynamically. </note></li>
<li>The encryption provider <p>An encryption provider implements the Java
cryptography concepts. The JRE for J2SE 1.4 or J2EE 1.4 includes JCE and one
Modified: db/derby/docs/trunk/src/devguide/cdevcsecure97760.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecure97760.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecure97760.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecure97760.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevcsecure97760" xml:lang="en-us">
<title>Working with encryption</title>
-<shortdesc>This section describes using encryption in <ph conref="devconrefs.dita#prod/productshortname"></ph>.</shortdesc>
+<shortdesc>This section describes using encryption in <ph conref="../conrefs.dita#prod/productshortname"></ph>.</shortdesc>
<prolog><metadata>
<keywords><indexterm>encryption<indexterm>working with</indexterm></indexterm>
</keywords>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecuree.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecuree.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecuree.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecuree.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
-->
<concept id="cdevcsecuree" xml:lang="en-us">
<title>Derby and Security</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> can be
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> can be
deployed in a number of ways and in a number of different environments. The
-security needs of the <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+security needs of the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
are also diverse.</shortdesc>
<prolog><metadata>
<keywords><indexterm>user authentication<indexterm>definition</indexterm></indexterm>
@@ -30,20 +30,20 @@
encryption</indexterm><indexterm>encrypting databases</indexterm></keywords>
</metadata></prolog>
<conbody>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> supplies or supports
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> supplies or supports
the following optional security mechanisms:</p>
<ul>
-<li><i>User authentication</i> <p><ph conref="devconrefs.dita#prod/productshortname"></ph> verifies
-user names and passwords before permitting them access to the <ph conref="devconrefs.dita#prod/productshortname"></ph> system.</p></li>
+<li><i>User authentication</i> <p><ph conref="../conrefs.dita#prod/productshortname"></ph> verifies
+user names and passwords before permitting them access to the <ph conref="../conrefs.dita#prod/productshortname"></ph> system.</p></li>
<li><i>User authorization</i> <p>A means of granting specific users permission
to read a database or to write to a database.</p></li>
-<li><i>Disk encryption</i> <p>A means of encrypting <ph conref="devconrefs.dita#prod/productshortname"></ph> data
+<li><i>Disk encryption</i> <p>A means of encrypting <ph conref="../conrefs.dita#prod/productshortname"></ph> data
stored on disk.</p></li>
<li><i>Validation of Certificate for Signed Jar Files</i> <p>In a Java 2
-environment, <ph conref="devconrefs.dita#prod/productshortname"></ph> validates
+environment, <ph conref="../conrefs.dita#prod/productshortname"></ph> validates
certificates for classes loaded from signed jar files.</p> </li>
</ul>
-<p>The following figure shows some of the <ph conref="devconrefs.dita#prod/productshortname"></ph> security
+<p>The following figure shows some of the <ph conref="../conrefs.dita#prod/productshortname"></ph> security
mechanisms at work in a client/server environment. User authentication is
performed by accessing an LDAP Directory Service. The data in the database
is not encrypted in this trusted environment.<fig expanse="column"><title>Example
@@ -53,7 +53,7 @@
authorization to read and write data. The Derby database is a trusted environment
and the data is not encrypted.</alt></image>
</fig></p>
-<p>The following figure shows how another <ph conref="devconrefs.dita#prod/productshortname"></ph> security
+<p>The following figure shows how another <ph conref="../conrefs.dita#prod/productshortname"></ph> security
mechanism, disk encryption, protects data when the recipient might not know
how to protect data. It is useful for databases deployed in an embedded environment.<fig
expanse="column"><title>Example of using disk encryption to protect data.</title>
Modified: db/derby/docs/trunk/src/devguide/cdevcsecuregrantrevokeaccess.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecuregrantrevokeaccess.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecuregrantrevokeaccess.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecuregrantrevokeaccess.dita Fri Mar 30 08:17:01 2007
@@ -35,12 +35,12 @@
<p>The SQL standard authorization mode is a SQL2003 compatible access control
system. You enable the SQL standard authorization mode by setting the <codeph>derby.database.sqlAuthorization</codeph> property
to <codeph>TRUE</codeph>.</p>
-<p>While <ph conref="devconrefs.dita#prod/productshortname"></ph> has a simpler
+<p>While <ph conref="../conrefs.dita#prod/productshortname"></ph> has a simpler
database access mode which can be set to provide users with <varname>full</varname>, <varname>read-only</varname>,
or <varname>no access</varname> authorization, this simpler access mode is
less appropriate for most client-server database configurations. When users
or applications issue SQL statements directly against the database, the <ph
-conref="devconrefs.dita#prod/productshortname"></ph> SQL authorization mode
+conref="../conrefs.dita#prod/productshortname"></ph> SQL authorization mode
provides a more precise mechanism to limit the actions that users can take
on the database.</p>
<p>The GRANT statement is used to grant specific permissions to users. The
@@ -68,16 +68,16 @@
to the user <codeph>harry</codeph>. The SELECT privilege is later revoked
from user <codeph>harry</codeph>, but user <codeph>harry</codeph> has access
to table <codeph>t</codeph> through the PUBLIC privilege.</p><note othertype="Exception"
-type="other">When you create a view, trigger, or constraint, <ph conref="devconrefs.dita#prod/productshortname"></ph> first
+type="other">When you create a view, trigger, or constraint, <ph conref="../conrefs.dita#prod/productshortname"></ph> first
checks to determine if you have the required privileges at the user-level.
If you have the user-level privileges, the object is created and is dependent
on that user-level privilege. If you do not have the required privileges at
-the user-level, <ph conref="devconrefs.dita#prod/productshortname"></ph> checks
+the user-level, <ph conref="../conrefs.dita#prod/productshortname"></ph> checks
to determine if you have the required privileges at the PUBLIC level. If you
have the PUBLIC level privileges, the object is created and is dependent on
that PUBLIC level privilege. After the object is created, if the privilege
on which the object depends on is revoked, the object is automatically dropped. <ph
-conref="devconrefs.dita#prod/productshortname"></ph> does not try to determine
+conref="../conrefs.dita#prod/productshortname"></ph> does not try to determine
if you have other privileges that can replace the privileges that are being
revoked. <dl><dlentry>
<dt>Example 1</dt>
@@ -125,18 +125,18 @@
or EXECUTE permission on <codeph>f</codeph>. User <codeph>anita</codeph> grants
SELECT permission on view <codeph>s.v</codeph> to user <codeph>harry</codeph>.
When user <codeph>harry</codeph> issues a SELECT statement on the view <codeph>s.v</codeph>, <ph
-conref="devconrefs.dita#prod/productshortname"></ph> checks to determine if
+conref="../conrefs.dita#prod/productshortname"></ph> checks to determine if
user <codeph>harry</codeph> has SELECT permission on view<codeph>s.v</codeph>. <ph
-conref="devconrefs.dita#prod/productshortname"></ph> does not check to determine
+conref="../conrefs.dita#prod/productshortname"></ph> does not check to determine
if user <codeph>harry</codeph> has SELECT permission on <codeph>t1</codeph>,
or <codeph>t2</codeph>, or EXECUTE permission on <codeph>f</codeph>. </p><p>Permissions
on triggers and constraints work the same way as permissions on views. When
-a view, trigger, or constraint is created, <ph conref="devconrefs.dita#prod/productshortname"></ph> checks
+a view, trigger, or constraint is created, <ph conref="../conrefs.dita#prod/productshortname"></ph> checks
that the owner has the required permissions. Other users do not need to have
those permissions to perform actions on a view, trigger, or constraint. </p><p>If
the required permissions are revoked from the owner of a view, trigger, or
constraint, the object is dropped as part of the REVOKE statement.</p><p>See
-the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite> for more information
+the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite> for more information
on the GRANT and REVOKE statements.</p></section>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy12748.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy12748.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy12748.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy12748.dita Fri Mar 30 08:17:01 2007
@@ -28,10 +28,10 @@
a mechanism that allows an application to access resources defined in the
classpath without knowing where or how they are stored.</p>
<p>You do not need to make any changes to the way code interacts with <ph
-conref="devconrefs.dita#prod/productshortname"></ph> and its JDBC driver.
-An application can safely attempt to boot <ph conref="devconrefs.dita#prod/productshortname"></ph>,
+conref="../conrefs.dita#prod/productshortname"></ph> and its JDBC driver.
+An application can safely attempt to boot <ph conref="../conrefs.dita#prod/productshortname"></ph>,
even though it is already running, without any errors. Applications connect
-to <ph conref="devconrefs.dita#prod/productshortname"></ph> in the usual manner.</p>
+to <ph conref="../conrefs.dita#prod/productshortname"></ph> in the usual manner.</p>
<note>The method <i>getResource</i> is not supported.</note>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy15325.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy15325.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy15325.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy15325.dita Fri Mar 30 08:17:01 2007
@@ -18,7 +18,7 @@
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "../dtd/concept.dtd">
<concept xml:lang="en-us" id="cdevdeploy15325">
<title>Creating Derby databases for read-only use</title>
-<shortdesc>You can create <ph conref="devconrefs.dita#prod/productshortname"></ph> databases for use on read-only media such as
+<shortdesc>You can create <ph conref="../conrefs.dita#prod/productshortname"></ph> databases for use on read-only media such as
CD-ROMs.</shortdesc>
<prolog><metadata>
<keywords>
@@ -27,7 +27,7 @@
</metadata>
</prolog>
<conbody>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> databases in zip or jar files are also read-only databases.
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> databases in zip or jar files are also read-only databases.
Typically, read-only databases are deployed with an application in an embedded
environment.</p>
</conbody></concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy15818.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy15818.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy15818.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy15818.dita Fri Mar 30 08:17:01 2007
@@ -21,21 +21,21 @@
<concept id="cdevdeploy15818" xml:lang="en-us">
<title>Create jar files for your application</title>
<shortdesc>Include any Java classes in a jar file that are intended for <ph
-conref="devconrefs.dita#prod/productshortname"></ph> class loading, except
+conref="../conrefs.dita#prod/productshortname"></ph> class loading, except
the following classes:</shortdesc>
<prolog></prolog>
<conbody>
<ul>
<li>The standard Java packages (<i>java.*</i>, <codeph><i>javax.*</i></codeph>)
- <p><ph conref="devconrefs.dita#prod/productshortname"></ph> does not prevent
+ <p><ph conref="../conrefs.dita#prod/productshortname"></ph> does not prevent
you from storing such a jar file in the database, but these classes <i>are
never loaded</i> from the jar file.</p></li>
<li>The classes that are supplied with your Java environment (for example, <i>sun.*</i>)</li>
</ul>
-<p>A running <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<p>A running <ph conref="../conrefs.dita#prod/productshortname"></ph> system
can load classes from any number of jar files from any number of schemas and
databases.</p>
-<p>Create jar files intended for <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<p>Create jar files intended for <ph conref="../conrefs.dita#prod/productshortname"></ph> database
class loading the same way you create a jar file for inclusion in a user's
classpath. For example, consider an application targeted at travel agencies: </p>
<codeblock><b>jar cf travelagent.jar travelagent/*.class.</b></codeblock>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy17604.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy17604.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy17604.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy17604.dita Fri Mar 30 08:17:01 2007
@@ -27,7 +27,7 @@
<conbody>
<p>That is, when you install or replace a jar file within an SQL statement
or change the database jar "classpath" (the <i>derby.database.classpath</i> property<codeph><i>),</i></codeph> <ph
-conref="devconrefs.dita#prod/productshortname"></ph> is able to load the new
+conref="../conrefs.dita#prod/productshortname"></ph> is able to load the new
classes right away without your having to reboot.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy18716.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy18716.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy18716.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy18716.dita Fri Mar 30 08:17:01 2007
@@ -22,7 +22,7 @@
<title>Connecting to databases with ambiguous paths to databases in the file
system</title>
<shortdesc>Use the basic connection URL syntax only if the database path specified
-does not also point to a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+does not also point to a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
in the file system.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Connecting to databases<indexterm>when path is ambiguous
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy21645.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy21645.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy21645.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy21645.dita Fri Mar 30 08:17:01 2007
@@ -22,15 +22,15 @@
<title>Enable database class loading with a property</title>
<shortdesc>Once you have added one or more jar files to a database, you must
set the database jar "classpath" by including the jar file or files in the <i>derby.database.classpath</i> property
-to enable <ph conref="devconrefs.dita#prod/productshortname"></ph> to load
+to enable <ph conref="../conrefs.dita#prod/productshortname"></ph> to load
classes from the jar files.</shortdesc>
<prolog></prolog>
<conbody>
<p>This property, which behaves like a class path, specifies the jar files
to be searched for classes and resources and the order in which they are searched.
-If <ph conref="devconrefs.dita#prod/productshortname"></ph> does not find
+If <ph conref="../conrefs.dita#prod/productshortname"></ph> does not find
a needed class stored in the database, it can retrieve the class from the
-user's classpath. (<ph conref="devconrefs.dita#prod/productshortname"></ph> first
+user's classpath. (<ph conref="../conrefs.dita#prod/productshortname"></ph> first
looks in the user's classpath before looking in the database.)</p>
<ul>
<li>Separate jar files with a colon (:).</li>
@@ -42,9 +42,9 @@
<codeblock><b>CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.database.classpath',
'APP.ToursLogic:APP.ACCOUNTINGLOGIC')</b></codeblock>
-<p>See <i>"derby.database.classpath"</i> in <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite> for
+<p>See <i>"derby.database.classpath"</i> in <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite> for
more information about the property.</p>
-<note><ph conref="devconrefs.dita#prod/productshortname"></ph>'s class loader
+<note><ph conref="../conrefs.dita#prod/productshortname"></ph>'s class loader
looks first in the user's classpath for any needed classes, and then in the
database. To ensure class loading with the database class loader, remove classes
from the classpath.</note>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy23812.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy23812.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy23812.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy23812.dita Fri Mar 30 08:17:01 2007
@@ -22,7 +22,7 @@
<title>Add the jar file or files to the database</title>
<shortdesc>Use a set of procedures to install, replace, and remove jar files
in a database. When you install a jar file in a database, you give it a <ph
-conref="devconrefs.dita#prod/productshortname"></ph> jar name, which is an <codeph>SQL92Identifier</codeph>.</shortdesc>
+conref="../conrefs.dita#prod/productshortname"></ph> jar name, which is an <codeph>SQL92Identifier</codeph>.</shortdesc>
<prolog><metadata>
<keywords><indexterm>jar files<indexterm>installing, removing, and replacing</indexterm></indexterm>
</keywords>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy30736.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy30736.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy30736.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy30736.dita Fri Mar 30 08:17:01 2007
@@ -34,8 +34,8 @@
application deployment, since it reduces the potential for problems with a
user's classpath.</p>
<p>In an embedded environment, when application logic is stored in the database, <ph
-conref="devconrefs.dita#prod/productshortname"></ph> can access classes loaded
-by the <ph conref="devconrefs.dita#prod/productshortname"></ph> class loader
+conref="../conrefs.dita#prod/productshortname"></ph> can access classes loaded
+by the <ph conref="../conrefs.dita#prod/productshortname"></ph> class loader
from stored jar files. </p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy32171.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy32171.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy32171.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy32171.dita Fri Mar 30 08:17:01 2007
@@ -20,13 +20,13 @@
-->
<concept id="cdevdeploy32171" xml:lang="en-us">
<title>Deploying Derby applications</title>
-<shortdesc>Typically, once you have developed a <ph conref="devconrefs.dita#prod/productshortname"></ph> application
-and database, you package up the application, the <ph conref="devconrefs.dita#prod/productshortname"></ph> libraries,
+<shortdesc>Typically, once you have developed a <ph conref="../conrefs.dita#prod/productshortname"></ph> application
+and database, you package up the application, the <ph conref="../conrefs.dita#prod/productshortname"></ph> libraries,
and the database in some means for distribution to your users. This process
is called <i>deployment</i>.</shortdesc>
<prolog></prolog>
<conbody>
-<p>This section discusses issues for deploying <ph conref="devconrefs.dita#prod/productshortname"></ph> applications
+<p>This section discusses issues for deploying <ph conref="../conrefs.dita#prod/productshortname"></ph> applications
and databases.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy855368.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy855368.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy855368.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy855368.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevdeploy855368" xml:lang="en-us">
<title>Embedded deployment application overview</title>
-<shortdesc>In an embedded environment, <ph conref="devconrefs.dita#prod/productshortname"></ph> runs
+<shortdesc>In an embedded environment, <ph conref="../conrefs.dita#prod/productshortname"></ph> runs
in the same JVM as the application.</shortdesc>
<prolog><metadata>
<keywords><indexterm>embedded applications<indexterm>deploying</indexterm></indexterm>
@@ -31,11 +31,11 @@
</metadata></prolog>
<conbody>
<p>The application can be a single-user application or a multi-user application
-server. In the latter case, <ph conref="devconrefs.dita#prod/productshortname"></ph> runs
+server. In the latter case, <ph conref="../conrefs.dita#prod/productshortname"></ph> runs
embedded in the user-provided server framework, and any client applications
use user-provided connectivity or allow the application server to handle all
database interaction.</p>
-<fig id="cdevdeploy31527"><title><ph conref="devconrefs.dita#prod/productshortname"></ph> embedded
+<fig id="cdevdeploy31527"><title><ph conref="../conrefs.dita#prod/productshortname"></ph> embedded
in a single-user Java application</title>
<image href="embed_os.gif" placement="break"><alt>This figure shows the single-user
application and the Derby database engine inside the Java Virtual Machine.
@@ -50,23 +50,23 @@
and the Derby database engine. The application connects to the Derby database
engine. The Derby database engine connects to the Derby database.</alt></image>
</fig>
-<p>When a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<p>When a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
is embedded in a Java application, the database is dedicated to that single
application. If you deploy more than one copy of the application, <i>each
-application has its own copy of the database and <ph conref="devconrefs.dita#prod/productshortname"></ph> software</i>.
-A <ph conref="devconrefs.dita#prod/productshortname"></ph> server framework
+application has its own copy of the database and <ph conref="../conrefs.dita#prod/productshortname"></ph> software</i>.
+A <ph conref="../conrefs.dita#prod/productshortname"></ph> server framework
can work in multi-threaded, multi-connection mode and can even connect to
-more than one database at a time. A server framework, such as the <ph conref="devconrefs.dita#prod/productshortname"></ph> Network
+more than one database at a time. A server framework, such as the <ph conref="../conrefs.dita#prod/productshortname"></ph> Network
Server, can be used to manage multiple connections and handle network capabilities.
Some server framework solutions, such as WebSphere Application Server, provide
additional features such as web services and connection pooling. However,
-only one server framework at a time can operate against a <ph conref="devconrefs.dita#prod/productshortname"></ph> database.</p>
-<p>The <ph conref="devconrefs.dita#prod/productshortname"></ph> application
-accesses an embedded <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+only one server framework at a time can operate against a <ph conref="../conrefs.dita#prod/productshortname"></ph> database.</p>
+<p>The <ph conref="../conrefs.dita#prod/productshortname"></ph> application
+accesses an embedded <ph conref="../conrefs.dita#prod/productshortname"></ph> database
through the JDBC API. To connect, an application makes a call to the local <ph
-conref="devconrefs.dita#prod/productshortname"></ph> JDBC driver. Accessing
-the JDBC driver automatically starts the embedded <ph conref="devconrefs.dita#prod/productshortname"></ph> software.
+conref="../conrefs.dita#prod/productshortname"></ph> JDBC driver. Accessing
+the JDBC driver automatically starts the embedded <ph conref="../conrefs.dita#prod/productshortname"></ph> software.
The calling application is responsible for shutting down the embedded <ph
-conref="devconrefs.dita#prod/productshortname"></ph> database software. </p>
+conref="../conrefs.dita#prod/productshortname"></ph> database software. </p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy855655.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy855655.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy855655.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy855655.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevdeploy855655" xml:lang="en-us">
<title>Deploying Derby in an embedded environment</title>
-<shortdesc>You can embed <ph conref="devconrefs.dita#prod/productshortname"></ph> in
+<shortdesc>You can embed <ph conref="../conrefs.dita#prod/productshortname"></ph> in
any Java application (single- or multi-user) by deploying the following packages.</shortdesc>
<prolog><metadata>
<keywords><indexterm>derby.jar</indexterm><indexterm>embedded environments<indexterm>deployment
@@ -28,7 +28,7 @@
</metadata></prolog>
<conbody>
<ul>
-<li>The <ph conref="devconrefs.dita#prod/productshortname"></ph> library (<i>derby.jar</i>).</li>
+<li>The <ph conref="../conrefs.dita#prod/productshortname"></ph> library (<i>derby.jar</i>).</li>
<li>The libraries for the application. You have the option of storing these
libraries in the database.</li>
<li>The database or databases used by the application, in the context of their
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy856753.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy856753.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy856753.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy856753.dita Fri Mar 30 08:17:01 2007
@@ -22,7 +22,7 @@
<title>Class loading overview</title>
<shortdesc>You store application classes and resources by storing one or more
jar files in the database. Then your application can access classes loaded
-by <ph conref="devconrefs.dita#prod/productshortname"></ph> from the jar file
+by <ph conref="../conrefs.dita#prod/productshortname"></ph> from the jar file
and does not need to be coded in a particular way. The only difference is
the way in which you invoke the application.</shortdesc>
<prolog></prolog>
Modified: db/derby/docs/trunk/src/devguide/cdevdeploy857611.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdeploy857611.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdeploy857611.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdeploy857611.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevdeploy857611" xml:lang="en-us">
<title>Requirements for dynamic changes</title>
-<shortdesc>Certain conditions must be met for <ph conref="devconrefs.dita#prod/productshortname"></ph> to
+<shortdesc>Certain conditions must be met for <ph conref="../conrefs.dita#prod/productshortname"></ph> to
be able to load the new classes right away without you having to reboot.</shortdesc>
<prolog></prolog>
<conbody>
Modified: db/derby/docs/trunk/src/devguide/cdevdgpref11181.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdgpref11181.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdgpref11181.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdgpref11181.dita Fri Mar 30 08:17:01 2007
@@ -20,12 +20,12 @@
-->
<concept id="cdevdgpref11181" xml:lang="en-us">
<title>Purpose of this guide</title>
-<shortdesc>This guide explains how to use the core <ph conref="devconrefs.dita#prod/productshortname"></ph> technology
-and is for developers building <ph conref="devconrefs.dita#prod/productshortname"></ph> applications.</shortdesc>
+<shortdesc>This guide explains how to use the core <ph conref="../conrefs.dita#prod/productshortname"></ph> technology
+and is for developers building <ph conref="../conrefs.dita#prod/productshortname"></ph> applications.</shortdesc>
<prolog></prolog>
<conbody>
-<p>It describes basic <ph conref="devconrefs.dita#prod/productshortname"></ph> concepts,
-such as how you create and access <ph conref="devconrefs.dita#prod/productshortname"></ph> databases
-through JDBC procedures and how you can deploy <ph conref="devconrefs.dita#prod/productshortname"></ph> applications.</p>
+<p>It describes basic <ph conref="../conrefs.dita#prod/productshortname"></ph> concepts,
+such as how you create and access <ph conref="../conrefs.dita#prod/productshortname"></ph> databases
+through JDBC procedures and how you can deploy <ph conref="../conrefs.dita#prod/productshortname"></ph> applications.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdgpref23947.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdgpref23947.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdgpref23947.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdgpref23947.dita Fri Mar 30 08:17:01 2007
@@ -25,9 +25,9 @@
<conbody>
<ul>
<li><i><xref href="cdevdvlp19524.dita#cdevdvlp19524"></xref></i> <p>Basic
-details for using <ph conref="devconrefs.dita#prod/productshortname"></ph>,
+details for using <ph conref="../conrefs.dita#prod/productshortname"></ph>,
including loading the JDBC driver, specifying a database URL, and starting <ph
-conref="devconrefs.dita#prod/productshortname"></ph>.</p></li>
+conref="../conrefs.dita#prod/productshortname"></ph>.</p></li>
<li><i><xref href="cdevstart19524.dita#cdevstart19524"></xref></i> <p>Explains
the installation layout.</p></li>
<li><i><xref href="cdevdeploy32171.dita#cdevdeploy32171"></xref></i> <p>An
Modified: db/derby/docs/trunk/src/devguide/cdevdgpref24290.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdgpref24290.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdgpref24290.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdgpref24290.dita Fri Mar 30 08:17:01 2007
@@ -24,7 +24,7 @@
some SQL and Java.</shortdesc>
<prolog></prolog>
<conbody>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> users who are
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> users who are
not familiar with the SQL standard or the Java programming language will benefit
from consulting books on those subjects.</p>
</conbody>
Modified: db/derby/docs/trunk/src/devguide/cdevdgpref29520.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdgpref29520.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdgpref29520.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdgpref29520.dita Fri Mar 30 08:17:01 2007
@@ -22,8 +22,8 @@
<title>About this guide</title>
<prolog></prolog>
<conbody>
-<p>For general information about the <ph conref="devconrefs.dita#prod/productshortname"></ph> documentation,
+<p>For general information about the <ph conref="../conrefs.dita#prod/productshortname"></ph> documentation,
such as a complete list of books, conventions, and further reading, see <cite><ph
-conref="devconrefs.dita#pub/citgetstart"></ph></cite>.</p>
+conref="../conrefs.dita#pub/citgetstart"></ph></cite>.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp13018.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp13018.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp13018.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp13018.dita Fri Mar 30 08:17:01 2007
@@ -20,18 +20,18 @@
-->
<concept id="cdevdvlp13018" xml:lang="en-us">
<title>Defining the system directory</title>
-<shortdesc>You define the system directory when <ph conref="devconrefs.dita#prod/productshortname"></ph> starts
+<shortdesc>You define the system directory when <ph conref="../conrefs.dita#prod/productshortname"></ph> starts
up by specifying a Java <i>system property</i> called <codeph><i>derby.system.home</i></codeph>.</shortdesc>
<prolog></prolog>
<conbody>
-<p>If you do not specify the system directory when starting up <ph conref="devconrefs.dita#prod/productshortname"></ph>,
+<p>If you do not specify the system directory when starting up <ph conref="../conrefs.dita#prod/productshortname"></ph>,
the current directory becomes the system directory.</p>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> uses the <i>derby.system.home</i> property
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> uses the <i>derby.system.home</i> property
to determine which directory is its system directory - and thus what databases
are in its system, where to create new databases, and what configuration parameters
-to use. See <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite> for
+to use. See <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite> for
more information on setting this property.</p>
-<p>If you specify a system directory at startup that does not exist, <ph conref="devconrefs.dita#prod/productshortname"></ph> creates
+<p>If you specify a system directory at startup that does not exist, <ph conref="../conrefs.dita#prod/productshortname"></ph> creates
this new directory - and thus a new system with no databases-automatically.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp14839.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp14839.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp14839.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp14839.dita Fri Mar 30 08:17:01 2007
@@ -20,45 +20,45 @@
-->
<concept id="cdevdvlp14839" xml:lang="en-us">
<title>Application development overview</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> application
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> application
developers use JDBC, the application programming interface that makes it possible
to access relational databases from Java programs.</shortdesc>
<prolog></prolog>
<conbody>
<p>The JDBC API is part of the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
tmtype="tm" trademark="Java">Java</tm> 2 Platform, Standard Edition and is
-not specific to <ph conref="devconrefs.dita#prod/productshortname"></ph>.
+not specific to <ph conref="../conrefs.dita#prod/productshortname"></ph>.
It consists of the <i>java.sql</i> and <i>javax.sql</i> packages, which is
a set of classes and interfaces that make it possible to access databases
-(from a number of different vendors, not just <ph conref="devconrefs.dita#prod/productshortname"></ph>)
+(from a number of different vendors, not just <ph conref="../conrefs.dita#prod/productshortname"></ph>)
from a Java application.</p>
-<p>To develop <ph conref="devconrefs.dita#prod/productshortname"></ph> applications
+<p>To develop <ph conref="../conrefs.dita#prod/productshortname"></ph> applications
successfully, you will need to learn JDBC. This section does not teach you
how to program with the JDBC API.</p>
<p>This section covers the details of application programming that are specific
-to <ph conref="devconrefs.dita#prod/productshortname"></ph> applications.
+to <ph conref="../conrefs.dita#prod/productshortname"></ph> applications.
For example, all JDBC applications typically start their DBMS's JDBC driver
and use a connection URL to connect to a database. This chapter gives you
-the details of how to start <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
-JDBC driver and how to work with <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
-connection URL to accomplish various tasks. It also covers essential <ph conref="devconrefs.dita#prod/productshortname"></ph> concepts
-such as the <ph conref="devconrefs.dita#prod/productshortname"></ph> system.</p>
-<p>You will find reference information about the particulars of <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
-implementation of JDBC in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>. </p>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> application developers
+the details of how to start <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
+JDBC driver and how to work with <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
+connection URL to accomplish various tasks. It also covers essential <ph conref="../conrefs.dita#prod/productshortname"></ph> concepts
+such as the <ph conref="../conrefs.dita#prod/productshortname"></ph> system.</p>
+<p>You will find reference information about the particulars of <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
+implementation of JDBC in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>. </p>
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> application developers
will need to learn SQL. <i>SQL</i> is the standard query language used with
relational databases and is not tied to a particular programming language.
No matter how a particular RDBMS has been implemented, the user can design
databases and insert, modify, and retrieve data using the standard SQL statements
and well-defined data types. SQL-92 is the version of SQL standardized by
-ANSI and ISO in 1992; <ph conref="devconrefs.dita#prod/productshortname"></ph> supports
+ANSI and ISO in 1992; <ph conref="../conrefs.dita#prod/productshortname"></ph> supports
entry-level SQL-92 as well as some higher-level features. Entry-level SQL-92
is a subset of full SQL-92 specified by ANSI and ISO that is supported by
nearly all major DBMSs today. This chapter does not teach you SQL. You will
-find reference information about the particulars of <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
-implementation of SQL in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> implements JDBC
-that allows <ph conref="devconrefs.dita#prod/productshortname"></ph> to serve
+find reference information about the particulars of <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
+implementation of SQL in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> implements JDBC
+that allows <ph conref="../conrefs.dita#prod/productshortname"></ph> to serve
as a resource manager in a J2EE compliant system.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp17453.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp17453.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp17453.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp17453.dita Fri Mar 30 08:17:01 2007
@@ -35,18 +35,18 @@
you to perform a number of high-level tasks, such as creating a database or
shutting down the system.</p>
<p>An application in an embedded environment uses a different connection URL
-from that used by applications using the <ph conref="devconrefs.dita#prod/productshortname"></ph> Network
-Server in a client/server environment. See the <cite><ph conref="devconrefs.dita#pub/citadmin"></ph></cite> for
+from that used by applications using the <ph conref="../conrefs.dita#prod/productshortname"></ph> Network
+Server in a client/server environment. See the <cite><ph conref="../conrefs.dita#pub/citadmin"></ph></cite> for
more information on the Network Server. </p>
<p>However, all versions of the connection URL (which you can use for tasks
besides connecting to a database) have common features:</p>
<ul>
<li>you can specify the name of the database you want to connect to</li>
<li>you can specify a number of attributes and values that allow you to accomplish
-tasks. For more information about what you can specify with the <ph conref="devconrefs.dita#prod/productshortname"></ph> connection
+tasks. For more information about what you can specify with the <ph conref="../conrefs.dita#prod/productshortname"></ph> connection
URL, see "Examples". For detailed reference about attributes and values, as
-well as syntax of the database connection URL, see the "<ph conref="devconrefs.dita#prod/productshortname"></ph> Database
-Connection URL Syntax" in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>. </li>
+well as syntax of the database connection URL, see the "<ph conref="../conrefs.dita#prod/productshortname"></ph> Database
+Connection URL Syntax" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>. </li>
</ul>
<p>An example use of the connection URL:</p>
<codeblock>Connection conn=DriverManager.getConnection("jdbc:derby:sample");</codeblock>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp18166.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp18166.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp18166.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp18166.dita Fri Mar 30 08:17:01 2007
@@ -20,8 +20,8 @@
-->
<concept id="cdevdvlp18166" xml:lang="en-us">
<title>Storage and recovery</title>
-<shortdesc>A <ph conref="devconrefs.dita#prod/productshortname"></ph> database
-provides persistent storage and recovery. <ph conref="devconrefs.dita#prod/productshortname"></ph> ensures
+<shortdesc>A <ph conref="../conrefs.dita#prod/productshortname"></ph> database
+provides persistent storage and recovery. <ph conref="../conrefs.dita#prod/productshortname"></ph> ensures
that all committed transactions are durable, even if the system fails, through
the use of a database transaction log.</shortdesc>
<prolog><metadata>
@@ -32,23 +32,23 @@
<p>Whereas inserts, updates, and deletes may be cached before being written
to disk, log entries tracking all those changes are never cached but always
forced to disk when a transaction commits. If the system or operating system
-fails unexpectedly, when <ph conref="devconrefs.dita#prod/productshortname"></ph> next
+fails unexpectedly, when <ph conref="../conrefs.dita#prod/productshortname"></ph> next
starts up it can use the log to perform recovery, recovering the "lost" transactions
from the log and rolling back uncommitted transactions. <i>Recovery</i> ensures
that all committed transactions at the time the system failed are applied
to the database, and all transactions that were active are rolled back. Thus
the databases are left in a consistent, valid state.</p>
-<p>In normal operation, <ph conref="devconrefs.dita#prod/productshortname"></ph> keeps
+<p>In normal operation, <ph conref="../conrefs.dita#prod/productshortname"></ph> keeps
the log small through periodic checkpoints. Checkpointing marks the portions
of the log that are no longer useful, writes changed pages to disk, then truncates
the log.</p>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> checkpoints the
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> checkpoints the
log file as it fills. It also checkpoints the log when a shutdown command
-is issued. Shutting down the JVM in which <ph conref="devconrefs.dita#prod/productshortname"></ph> is
+is issued. Shutting down the JVM in which <ph conref="../conrefs.dita#prod/productshortname"></ph> is
running without issuing the proper shutdown command is equivalent to a system
-failure from <ph conref="devconrefs.dita#prod/productshortname"></ph>'s point
+failure from <ph conref="../conrefs.dita#prod/productshortname"></ph>'s point
of view.</p>
-<p>Booting a database means that <ph conref="devconrefs.dita#prod/productshortname"></ph> checks
+<p>Booting a database means that <ph conref="../conrefs.dita#prod/productshortname"></ph> checks
to see if recovery needs to be run on a database. Recovery can be costly,
so using the proper shutdown command improves connection or startup performance.</p>
</conbody>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp19297.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp19297.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp19297.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp19297.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevdvlp19297" xml:lang="en-us">
<title>Recommended practices</title>
-<shortdesc>When developing <ph conref="devconrefs.dita#prod/productshortname"></ph> applications,
+<shortdesc>When developing <ph conref="../conrefs.dita#prod/productshortname"></ph> applications,
create a single directory to hold your database or databases.</shortdesc>
<prolog><metadata>
<keywords><indexterm>System directory<indexterm>creating and naming directory
@@ -38,10 +38,10 @@
your databases there is the recommended practice.)</li>
<li>Once you connect to a database, it is part of the current system and thus
inherits all system-wide properties.</li>
-<li>Only one instance of <ph conref="devconrefs.dita#prod/productshortname"></ph> can
-run in a JVM at a single time, and only one instance of <ph conref="devconrefs.dita#prod/productshortname"></ph> should
+<li>Only one instance of <ph conref="../conrefs.dita#prod/productshortname"></ph> can
+run in a JVM at a single time, and only one instance of <ph conref="../conrefs.dita#prod/productshortname"></ph> should
boot a database at one time. Keeping databases in the system directory makes
-it less likely that you would use more than one instance of <ph conref="devconrefs.dita#prod/productshortname"></ph>.</li>
+it less likely that you would use more than one instance of <ph conref="../conrefs.dita#prod/productshortname"></ph>.</li>
<li>The error log is located inside the system directory.</li>
</ul></p>
</conbody>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp19524.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp19524.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp19524.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp19524.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
-->
<concept id="cdevdvlp19524" xml:lang="en-us">
<title>JDBC applications and Derby basics</title>
-<shortdesc>This section describes the core <ph conref="devconrefs.dita#prod/productshortname"></ph> functionality.
-In addition, it details the most basic <ph conref="devconrefs.dita#prod/productshortname"></ph> deployment, <ph
-conref="devconrefs.dita#prod/productshortname"></ph> embedded in a Java application.</shortdesc>
+<shortdesc>This section describes the core <ph conref="../conrefs.dita#prod/productshortname"></ph> functionality.
+In addition, it details the most basic <ph conref="../conrefs.dita#prod/productshortname"></ph> deployment, <ph
+conref="../conrefs.dita#prod/productshortname"></ph> embedded in a Java application.</shortdesc>
<prolog></prolog>
<conbody></conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp20458.dita Fri Mar 30 08:17:01 2007
@@ -20,27 +20,27 @@
-->
<concept id="cdevdvlp20458" xml:lang="en-us">
<title>Double-booting system behavior</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> attempts
-to prevent two instances of <ph conref="devconrefs.dita#prod/productshortname"></ph> from
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> attempts
+to prevent two instances of <ph conref="../conrefs.dita#prod/productshortname"></ph> from
booting the same database by using a file called <i>db.lck</i> inside the
database directory.</shortdesc>
<prolog></prolog>
<conbody>
-<p>On all platforms running with a JDK of 1.4 or higher, <ph conref="devconrefs.dita#prod/productshortname"></ph> can
-successfully prevent a second instance of <ph conref="devconrefs.dita#prod/productshortname"></ph> from
+<p>On all platforms running with a JDK of 1.4 or higher, <ph conref="../conrefs.dita#prod/productshortname"></ph> can
+successfully prevent a second instance of <ph conref="../conrefs.dita#prod/productshortname"></ph> from
booting the database and thus prevents corruption.</p>
-<p>On some platforms running with a JDK lower than 1.4, <ph conref="devconrefs.dita#prod/productshortname"></ph> may
-prevent a second instance of <ph conref="devconrefs.dita#prod/productshortname"></ph> from
+<p>On some platforms running with a JDK lower than 1.4, <ph conref="../conrefs.dita#prod/productshortname"></ph> may
+prevent a second instance of <ph conref="../conrefs.dita#prod/productshortname"></ph> from
booting the database (previous to JDK 1.4 the ability to do this was OS dependent).</p>
<p>If this is the case, you will see an <i>SQLException</i> like the following:</p>
<codeblock>ERROR XJ040: Failed to start database 'sample', see the next exception for details.
-ERROR XSDB6: Another instance of <ph conref="devconrefs.dita#prod/productshortname"></ph> might have already booted
+ERROR XSDB6: Another instance of <ph conref="../conrefs.dita#prod/productshortname"></ph> might have already booted
the databaseC:\databases\sample.
</codeblock>
<p>The error is also written to the error log.</p>
-<p>If you are running a JVM prior to 1.4, <ph conref="devconrefs.dita#prod/productshortname"></ph> issues
-a warning message on some platforms if an instance of <ph conref="devconrefs.dita#prod/productshortname"></ph> attempts
-to boot a database that already has a running instance of <ph conref="devconrefs.dita#prod/productshortname"></ph> attached
+<p>If you are running a JVM prior to 1.4, <ph conref="../conrefs.dita#prod/productshortname"></ph> issues
+a warning message on some platforms if an instance of <ph conref="../conrefs.dita#prod/productshortname"></ph> attempts
+to boot a database that already has a running instance of <ph conref="../conrefs.dita#prod/productshortname"></ph> attached
to it. However, it does not prevent the second instance from booting, and
thus potentially corrupting, the database. (You can change this behavior with
the property <codeph><i>derby.database.forceDatabaseLock</i></codeph>.)</p>
@@ -49,46 +49,46 @@
access to the database.</p>
<p>The warning message looks like this:</p>
<codeblock>
-WARNING: <ph conref="devconrefs.dita#prod/productshortname"></ph>
+WARNING: <ph conref="../conrefs.dita#prod/productshortname"></ph>
(instance 80000000-00d2-3265-de92-000a0a0a0200) is
attempting to boot the database /export/home/sky/wombat
-even though <ph conref="devconrefs.dita#prod/productshortname"></ph>
+even though <ph conref="../conrefs.dita#prod/productshortname"></ph>
(instance 80000000-00d2-3265-8abf-000a0a0a0200) might still be active.
-Only one instance of <ph conref="devconrefs.dita#prod/productshortname"></ph>
+Only one instance of <ph conref="../conrefs.dita#prod/productshortname"></ph>
should boot a database at a time. Severe and non-recoverable corruption can
result and might have already occurred.</codeblock>
<p>The warning is also written to the error log.</p>
<p> If you see this warning, you should close the connection and exit the
-JVM, minimizing the risk of a corruption. Close all instances of <ph conref="devconrefs.dita#prod/productshortname"></ph>,
-then restart one instance of <ph conref="devconrefs.dita#prod/productshortname"></ph> and
+JVM, minimizing the risk of a corruption. Close all instances of <ph conref="../conrefs.dita#prod/productshortname"></ph>,
+then restart one instance of <ph conref="../conrefs.dita#prod/productshortname"></ph> and
shut down the database properly so that the <i>db.lck</i> file can be removed.
The warning message continues to appear until a proper shutdown of the <ph
-conref="devconrefs.dita#prod/productshortname"></ph> system can delete the <i>db.lck</i> file.</p>
-<p>When developing applications, you might want to configure <ph conref="devconrefs.dita#prod/productshortname"></ph> to
+conref="../conrefs.dita#prod/productshortname"></ph> system can delete the <i>db.lck</i> file.</p>
+<p>When developing applications, you might want to configure <ph conref="../conrefs.dita#prod/productshortname"></ph> to
append to the log. Doing so will help you detect when you have inadvertently
-started more than one instance of <ph conref="devconrefs.dita#prod/productshortname"></ph> in
+started more than one instance of <ph conref="../conrefs.dita#prod/productshortname"></ph> in
the same system. For example, when the <i>derby.infolog.append</i> property
-is set to true for a system, booting two instances of <ph conref="devconrefs.dita#prod/productshortname"></ph> in
+is set to true for a system, booting two instances of <ph conref="../conrefs.dita#prod/productshortname"></ph> in
the same system produces the following in the log:</p>
<codeblock>Sat Aug 14 09:42:51 PDT 2005:
-Booting <ph conref="devconrefs.dita#prod/productshortname"></ph> version <ph
-conref="devconrefs.dita#prod/productlongname"></ph> - 10.0.0.1 - (29612):
+Booting <ph conref="../conrefs.dita#prod/productshortname"></ph> version <ph
+conref="../conrefs.dita#prod/productlongname"></ph> - 10.0.0.1 - (29612):
instance 80000000-00d2-1c87-7586-000a0a0b1300 on database at
directory C:\tutorial_system\sample
------------------------------------------------------------
Sat Aug 14 09:42:59 PDT 2005:
-Booting <ph conref="devconrefs.dita#prod/productshortname"></ph> version <ph
-conref="devconrefs.dita#prod/productlongname"></ph> - 10.0.0.1 - (29612):
+Booting <ph conref="../conrefs.dita#prod/productshortname"></ph> version <ph
+conref="../conrefs.dita#prod/productlongname"></ph> - 10.0.0.1 - (29612):
instance 80000000-00d2-1c87-9143-000a0a0b1300 on database at
directory C:\tutorial_system\HelloWorldDB</codeblock>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> allows you to
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> allows you to
boot databases that are not in the system directory. While this might seem
more convenient, check that you do not boot the same database with two JVMs.
If you need to access a single database from more than one JVM, you will need
to put a server solution in place. You can allow multiple JVMs that need to
-access that database to connect to the server. The <ph conref="devconrefs.dita#prod/productshortname"></ph> Network
-Server is provided as a server solution. See the <cite><ph conref="devconrefs.dita#pub/citadmin"></ph></cite> for
+access that database to connect to the server. The <ph conref="../conrefs.dita#prod/productshortname"></ph> Network
+Server is provided as a server solution. See the <cite><ph conref="../conrefs.dita#pub/citadmin"></ph></cite> for
more information on the Network Server.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp21955.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp21955.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp21955.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp21955.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
-->
<concept id="cdevdvlp21955" xml:lang="en-us">
<title>A Derby database</title>
-<shortdesc>A <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<shortdesc>A <ph conref="../conrefs.dita#prod/productshortname"></ph> database
contains dictionary objects such as tables, columns, indexes, and jar files.
-A <ph conref="devconrefs.dita#prod/productshortname"></ph> database can also
+A <ph conref="../conrefs.dita#prod/productshortname"></ph> database can also
store its own configuration information.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Databases<indexterm>description of in Derby system</indexterm></indexterm>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp22619.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp22619.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp22619.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp22619.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
<concept id="cdevdvlp22619" xml:lang="en-us">
<title>Working with database threads in an embedded environment</title>
<shortdesc>Do not use <codeph><i>interrupt</i></codeph> calls to notify threads
-that are accessing a database, because <ph conref="devconrefs.dita#prod/productshortname"></ph> will
+that are accessing a database, because <ph conref="../conrefs.dita#prod/productshortname"></ph> will
catch the <codeph><i>interrupt</i></codeph> call and close the connection
to the database. Use <codeph><i>wait</i></codeph> and <codeph><i>notify</i></codeph> calls
instead.</shortdesc>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp24155.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp24155.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp24155.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp24155.dita Fri Mar 30 08:17:01 2007
@@ -27,7 +27,7 @@
<note>All such databases are read-only.</note>
<p>For example, suppose you have archived the database <i>jarDB1</i> into
a file called <i>jar1.jar</i>. This archive is in the classpath before you
-start up <ph conref="devconrefs.dita#prod/productshortname"></ph>. You can
+start up <ph conref="../conrefs.dita#prod/productshortname"></ph>. You can
access <i>jarDB1</i> with the following connection URL</p>
<codeblock>jdbc:derby:/jarDB1</codeblock>
<p>To access a database in a jar file that is not on the classpath, use the
@@ -37,7 +37,7 @@
access <i>jarDB2</i> by specifying the path to the jar file along with the
jar subsubprotocol, like this:</p>
<codeblock>
-jdbc:derby:jar:(c:/<ph conref="devconrefs.dita#prod/productlowercase"></ph>/lib/jar2.jar)jarDB2
+jdbc:derby:jar:(c:/<ph conref="../conrefs.dita#prod/productlowercase"></ph>/lib/jar2.jar)jarDB2
</codeblock>
<p>For complete instructions and examples of accessing databases in jar files,
see <xref href="cdevdeploy11201.dita#cdevdeploy11201"></xref>.</p>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp25174.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp25174.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp25174.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp25174.dita Fri Mar 30 08:17:01 2007
@@ -20,12 +20,12 @@
-->
<concept id="cdevdvlp25174" xml:lang="en-us">
<title>Derby embedded basics</title>
-<shortdesc>This section explains how to use and configure <ph conref="devconrefs.dita#prod/productshortname"></ph> in
+<shortdesc>This section explains how to use and configure <ph conref="../conrefs.dita#prod/productshortname"></ph> in
an embedded environment.</shortdesc>
<prolog></prolog>
<conbody>
<p>Included in the installation is a sample application program, <i>/demo/programs/simple</i>,
-which illustrates how to run <ph conref="devconrefs.dita#prod/productshortname"></ph> embedded
+which illustrates how to run <ph conref="../conrefs.dita#prod/productshortname"></ph> embedded
in the calling program.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp25820.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp25820.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp25820.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp25820.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevdvlp25820" xml:lang="en-us">
<title>Database pages</title>
-<shortdesc><ph conref="devconrefs.dita#prod/productshortname"></ph> tables
+<shortdesc><ph conref="../conrefs.dita#prod/productshortname"></ph> tables
and indexes, known as conglomerates, consist of two or more pages.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Database pages<indexterm>description</indexterm></indexterm>
@@ -32,7 +32,7 @@
grows one page at a time until eight pages of user data (or nine pages of
total disk use, which includes one page of internal information) have been
allocated. (You can configure this behavior; see <i>"derby.storage.initialPages" </i> in <cite><ph
-conref="devconrefs.dita#pub/cittuning"></ph></cite>.) After that, it grows
+conref="../conrefs.dita#pub/cittuning"></ph></cite>.) After that, it grows
eight pages at a time.</p>
<p>The size of a row or column is not limited by the page size. Rows or columns
that are longer than the table's page size are automatically wrapped to overflow
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp25889.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp25889.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp25889.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp25889.dita Fri Mar 30 08:17:01 2007
@@ -20,20 +20,20 @@
-->
<concept id="cdevdvlp25889" xml:lang="en-us">
<title>The error log</title>
-<shortdesc>Once you create or connect to a database within a system, <ph conref="devconrefs.dita#prod/productshortname"></ph> begins
+<shortdesc>Once you create or connect to a database within a system, <ph conref="../conrefs.dita#prod/productshortname"></ph> begins
outputting information and error messages to the error log.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Error log<indexterm>description</indexterm></indexterm>
</keywords>
</metadata></prolog>
<conbody>
-<p>Typically, <ph conref="devconrefs.dita#prod/productshortname"></ph> writes
+<p>Typically, <ph conref="../conrefs.dita#prod/productshortname"></ph> writes
this information to a log called <i>derby.log</i> in the system directory,
-although you can also have <ph conref="devconrefs.dita#prod/productshortname"></ph> send
+although you can also have <ph conref="../conrefs.dita#prod/productshortname"></ph> send
messages to a stream, using the <codeph>derby.stream.error.method</codeph> property.
-By default, <ph conref="devconrefs.dita#prod/productshortname"></ph> overwrites <i>derby.log</i> when
-you start the system. You can configure <ph conref="devconrefs.dita#prod/productshortname"></ph> to
+By default, <ph conref="../conrefs.dita#prod/productshortname"></ph> overwrites <i>derby.log</i> when
+you start the system. You can configure <ph conref="../conrefs.dita#prod/productshortname"></ph> to
append to the log with the <codeph>derby.infolog.append</codeph> property.
-For information on setting this and other properties, see <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>.</p>
+For information on setting this and other properties, see <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite>.</p>
</conbody>
</concept>
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp27610.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp27610.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp27610.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp27610.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<concept id="cdevdvlp27610" xml:lang="en-us">
<title>Derby system</title>
-<shortdesc>A <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<shortdesc>A <ph conref="../conrefs.dita#prod/productshortname"></ph> database
exists within a <i>system</i>.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Derby system</indexterm><indexterm>System directory</indexterm>
@@ -29,20 +29,20 @@
<indexterm>Error log</indexterm><indexterm>derby.log</indexterm></keywords>
</metadata></prolog>
<conbody>
-<p>A <ph conref="devconrefs.dita#prod/productshortname"></ph> system is a
-single instance of the <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<p>A <ph conref="../conrefs.dita#prod/productshortname"></ph> system is a
+single instance of the <ph conref="../conrefs.dita#prod/productshortname"></ph> database
engine and the environment in which it runs. It consists of a system directory,
zero or more databases, and a system-wide configuration. The system directory
contains any persistent system-wide configuration parameters, or properties,
specific to that system in a properties file called <xref href="cdevdvlp39943.dita#cdevdvlp39943">derby.properties</xref>.
This file is not automatically created; you must create it yourself.</p>
-<p>The <ph conref="devconrefs.dita#prod/productshortname"></ph> system is
+<p>The <ph conref="../conrefs.dita#prod/productshortname"></ph> system is
not persistent; you must specify the location of the system directory at every
startup.</p>
-<p>However, the <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<p>However, the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
and the system directory is an essential part of a running database or databases.
-Understanding the <ph conref="devconrefs.dita#prod/productshortname"></ph> system
-is essential to successful development and deployment of <ph conref="devconrefs.dita#prod/productshortname"></ph> applications.
+Understanding the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
+is essential to successful development and deployment of <ph conref="../conrefs.dita#prod/productshortname"></ph> applications.
Derby databases live in a system, which includes system-wide properties, an
error log, and one or more databases.</p>
<fig expanse="column" id="rdevdvlp17155"><title>Derby databases live in a