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 [4/4] - /db/derby/docs/trunk/src/devguide/
Modified: db/derby/docs/trunk/src/devguide/rdevconcepts8424.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevconcepts8424.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevconcepts8424.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevconcepts8424.dita Fri Mar 30 08:17:01 2007
@@ -42,27 +42,27 @@
locking instead of row-level locking for performance reasons is called <i>lock
escalation</i>. For more information about this topic, see "About the System's
Selection of Lock Granularity" and "Transaction-Based Lock Escalation" in <cite><ph
-conref="devconrefs.dita#pub/cittuning"></ph></cite>.</p></section>
+conref="../conrefs.dita#pub/cittuning"></ph></cite>.</p></section>
<section><title>Single-row locks</title><p>A statement can lock only <i>a
single row</i> at a time.</p><p>For row-level locking systems:<ul>
<li>For TRANSACTION_REPEATABLE_READ isolation, the locks are released at the
end of the transaction.</li>
-<li>For TRANSACTION_READ_COMMITTED isolation, <ph conref="devconrefs.dita#prod/productshortname"></ph> locks
+<li>For TRANSACTION_READ_COMMITTED isolation, <ph conref="../conrefs.dita#prod/productshortname"></ph> locks
rows only as the application steps through the rows in the result. The current
row is locked. The row lock is released when the application goes to the next
row.</li>
-<li>For TRANSACTION_SERIALIZABLE isolation, however, <ph conref="devconrefs.dita#prod/productshortname"></ph> locks
+<li>For TRANSACTION_SERIALIZABLE isolation, however, <ph conref="../conrefs.dita#prod/productshortname"></ph> locks
the whole set before the application begins stepping through.</li>
<li>For TRANSACTION_READ_UNCOMMITTED, no row locks are requested.</li>
-</ul> </p><p><ph conref="devconrefs.dita#prod/productshortname"></ph> locks
+</ul> </p><p><ph conref="../conrefs.dita#prod/productshortname"></ph> locks
single rows for INSERT statements, holding each row until the transaction
is committed. If there is an index associated with the table, the previous
key is also locked.</p></section>
<section><title>Range locks</title><p>A statement can lock <i>a range of rows</i> (range
lock).</p><p>For row-level locking systems: <ul>
-<li>For <i>any</i> isolation level, <ph conref="devconrefs.dita#prod/productshortname"></ph> locks <i>all
+<li>For <i>any</i> isolation level, <ph conref="../conrefs.dita#prod/productshortname"></ph> locks <i>all
the rows in the result</i> plus an entire range of rows for updates or deletes.</li>
-<li>For the TRANSACTION_SERIALIZABLE isolation level, <ph conref="devconrefs.dita#prod/productshortname"></ph> locks
+<li>For the TRANSACTION_SERIALIZABLE isolation level, <ph conref="../conrefs.dita#prod/productshortname"></ph> locks
all the rows in the result plus an entire range of rows in the table for SELECTs
to prevent nonrepeatable reads and phantoms.</li>
</ul></p><p>For example, if a SELECT statement specifies rows in the <i>Employee</i> table
@@ -70,7 +70,7 @@
just the actual rows it returns in the result. It also must lock the entire <i>range</i> of
rows between those two values to prevent another transaction from inserting,
deleting, or updating a row within that range.</p><p>An index must be available
-for a range lock. If one is not available, <ph conref="devconrefs.dita#prod/productshortname"></ph> locks
+for a range lock. If one is not available, <ph conref="../conrefs.dita#prod/productshortname"></ph> locks
the entire table.</p><table frame="all" id="cdevconcepts15873"><title>Types
and scopes of locking</title>
<tgroup cols="3" colsep="1" rowsep="1"><colspec colname="1" colnum="1" colwidth="1159*"/>
Modified: db/derby/docs/trunk/src/devguide/rdevconceptsholdablecursors.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevconceptsholdablecursors.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevconceptsholdablecursors.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevconceptsholdablecursors.dita Fri Mar 30 08:17:01 2007
@@ -27,7 +27,7 @@
<keywords><indexterm>Cursors<indexterm>holdable</indexterm></indexterm></keywords>
</metadata></prolog>
<refbody>
-<section> <note> <ph conref="devconrefs.dita#prod/productshortname"></ph>, supports
+<section> <note> <ph conref="../conrefs.dita#prod/productshortname"></ph>, supports
non-holdable result sets on platforms which support JDBC
3.</note>
</section>
@@ -49,7 +49,7 @@
</ul></section>
<section><p>The method <i>Statement.getResultSetHoldability()</i> indicates
whether a result set generated by the Statement object stays open or closes, upon
-commit. See the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite> for
+commit. See the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite> for
more information.</p></section>
<section><p>When an implicit or explicit commit occurs, result sets
that hold cursors open behave as follows:</p></section>
@@ -74,7 +74,7 @@
</ul></p></section>
<section> <note> Holdable result sets do not work with XA
transactions in <ph
-conref="devconrefs.dita#prod/productshortname"></ph>. When working
+conref="../conrefs.dita#prod/productshortname"></ph>. When working
with XA transactions, the result set should be opened with holdability
<codeph>ResultSet.CLOSE_CURSORS_AT_COMMIT</codeph>.</note></section>
</refbody>
Modified: db/derby/docs/trunk/src/devguide/rdevconceptssur.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevconceptssur.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevconceptssur.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevconceptssur.dita Fri Mar 30 08:17:01 2007
@@ -28,7 +28,7 @@
<section>
<p>
-<ph conref="devconrefs.dita#prod/productshortname"></ph> only supports
+<ph conref="../conrefs.dita#prod/productshortname"></ph> only supports
<xref href="cdevconcepts22641.dita">scrollable insensitive result sets.</xref>
To create a scrollable insensitive result set which is updatable, the
statement has to be created with concurrency mode
@@ -74,7 +74,7 @@
scrollable insensitive result sets. </li>
<li>Own updates and deletes are visible in Derby's scrollable
insensitive result sets. <note> <ph
-conref="devconrefs.dita#prod/productshortname"></ph> handles changes
+conref="../conrefs.dita#prod/productshortname"></ph> handles changes
made using positioned updates and deletes as own changes, so when made
via a result set's cursor such changes are also visible in that result
set.
Modified: db/derby/docs/trunk/src/devguide/rdevcsecure125.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevcsecure125.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevcsecure125.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevcsecure125.dita Fri Mar 30 08:17:01 2007
@@ -20,16 +20,16 @@
-->
<reference id="rdevcsecure125" xml:lang="en-us">
<title>User authentication example in a client/server environment</title>
-<shortdesc>In this example, <ph conref="devconrefs.dita#prod/productshortname"></ph> is
+<shortdesc>In this example, <ph conref="../conrefs.dita#prod/productshortname"></ph> is
running in a user-designed application server.</shortdesc>
<prolog></prolog>
<refbody>
-<section><p><ph conref="devconrefs.dita#prod/productshortname"></ph> provides
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> provides
the user authentication, not the application server. The server is running
in a secure environment, the application server encrypts the passwords, and
a database administrator is available. The administrator configures security
using system-level properties in the <i>derby.properties</i> file and has
-protected this file with operating system tools. <ph conref="devconrefs.dita#prod/productshortname"></ph> connects
+protected this file with operating system tools. <ph conref="../conrefs.dita#prod/productshortname"></ph> connects
to an existing LDAP directory service within the enterprise to authenticate
users.</p></section>
<section><p>The default access mode for all databases is set to <i>fullAccess</i> (the
@@ -47,7 +47,7 @@
<b># explicitly show the access mode for databases (this is default)</b>
derby.database.defaultAccessMode=fullAccess</codeblock></example>
<section><p>With these settings, all users must be authenticated by the LDAP
-server in order to access any <ph conref="devconrefs.dita#prod/productshortname"></ph> databases.</p></section>
+server in order to access any <ph conref="../conrefs.dita#prod/productshortname"></ph> databases.</p></section>
<section><p>The database administrator has determined that one database, <i>accountingDB</i>,
has additional security needs. Within a connection to that database, the database
administrator uses database-wide properties (which override properties set
Modified: db/derby/docs/trunk/src/devguide/rdevcsecure13713.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevcsecure13713.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevcsecure13713.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevcsecure13713.dita Fri Mar 30 08:17:01 2007
@@ -20,13 +20,13 @@
-->
<reference id="rdevcsecure13713" xml:lang="en-us">
<title>User authentication example in a single-user, embedded environment</title>
-<shortdesc>In this example, <ph conref="devconrefs.dita#prod/productshortname"></ph> is
+<shortdesc>In this example, <ph conref="../conrefs.dita#prod/productshortname"></ph> is
embedded in a single-user application that is deployed in a number of different
and potentially insecure ways.</shortdesc>
<prolog></prolog>
<refbody>
<section><p>For that reason, the application developer has decided to encrypt
-the database and to turn on user authentication using <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+the database and to turn on user authentication using <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
built-in user authentication, which will not require connections to an LDAP
server. The end-user must know the <i>bootPassword</i> to boot the database
and the user name and password to connect to the database. Even if the database
Modified: db/derby/docs/trunk/src/devguide/rdevcsecure26537.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevcsecure26537.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevcsecure26537.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevcsecure26537.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
<reference id="rdevcsecure26537" xml:lang="en-us">
<title>User authentication and authorization extended examples</title>
<shortdesc>The following two examples from the <i>sample</i> database show
-how to turn on and turn off user authentication using <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+how to turn on and turn off user authentication using <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
built-in user authentication and user authorization.</shortdesc>
<prolog></prolog>
<refbody>
@@ -44,7 +44,7 @@
"'derby.connection.requireAuthentication')");
rs.next();
System.out.println(rs.getString(1));
- // Setting authentication scheme to <ph conref="devconrefs.dita#prod/productshortname"></ph>
+ // Setting authentication scheme to <ph conref="../conrefs.dita#prod/productshortname"></ph>
s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +
"'derby.authentication.provider', 'BUILTIN')");
Modified: db/derby/docs/trunk/src/devguide/rdevcsecure379.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevcsecure379.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevcsecure379.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevcsecure379.dita Fri Mar 30 08:17:01 2007
@@ -26,7 +26,7 @@
</keywords>
</metadata></prolog>
<refbody>
-<section><p><ph conref="devconrefs.dita#prod/productshortname"></ph> validates
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> validates
the database properties when you set the properties. An exception is returned
if you specify an invalid value when you set these properties. </p><p>After
you set the <codeph>derby.database.sqlAuthorization</codeph> property to <varname>TRUE</varname>,
Modified: db/derby/docs/trunk/src/devguide/rdevcsecure557.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevcsecure557.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevcsecure557.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevcsecure557.dita Fri Mar 30 08:17:01 2007
@@ -57,7 +57,7 @@
<row>
<entry colname="1"><i>derby.user.UserName</i></entry>
<entry colname="2">Creates a user name and password for the built-in user
-repository in<ph conref="devconrefs.dita#prod/productshortname"></ph>.</entry>
+repository in<ph conref="../conrefs.dita#prod/productshortname"></ph>.</entry>
</row>
<row>
<entry colname="1"><i>java.naming.*</i></entry>
Modified: db/derby/docs/trunk/src/devguide/rdevcsecure608.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevcsecure608.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevcsecure608.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevcsecure608.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<reference id="rdevcsecure608" xml:lang="en-us">
<title>Libraries for LDAP user authentication</title>
-<shortdesc>To use an LDAP directory service with <ph conref="devconrefs.dita#prod/productshortname"></ph>,
+<shortdesc>To use an LDAP directory service with <ph conref="../conrefs.dita#prod/productshortname"></ph>,
you need these libraries in your classpath.</shortdesc>
<prolog><metadata>
<keywords><indexterm>jndid<indexterm>required for LDAP user authorization</indexterm></indexterm>
@@ -34,7 +34,7 @@
<li><i>ldap.jar</i> <p>LDAP provider from Sun</p></li>
<li><i>providerutil.jar</i> <p>JNDI classes for a provider</p></li>
</ul></section>
-<section><p><ph conref="devconrefs.dita#prod/productshortname"></ph> does
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> does
not provide these libraries; they are available from Sun on the JNDI page.
Use the 1.1.x versions of these libraries, not the 1.2.x versions. You might
need to do two separate downloads to obtain all the required libraries.</p></section>
Modified: db/derby/docs/trunk/src/devguide/rdevcsecure766.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevcsecure766.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevcsecure766.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevcsecure766.dita Fri Mar 30 08:17:01 2007
@@ -41,11 +41,11 @@
Connection conn = DriverManager.getConnection(
"jdbc:derby:myDB", p);</codeblock></li>
</ul></section>
-<section> <note>The password is not encrypted. When you are using <ph conref="devconrefs.dita#prod/productshortname"></ph> in
+<section> <note>The password is not encrypted. When you are using <ph conref="../conrefs.dita#prod/productshortname"></ph> in
the context of a server framework, the framework should be responsible for
encrypting the password across the network. If your framework does not encrypt
the password, consider using SSL. </note></section>
<section><p>For information about the treatment of user names within the <ph
-conref="devconrefs.dita#prod/productshortname"></ph> system, see <xref href="cdevcsecure37241.dita#cdevcsecure37241"></xref>.</p></section>
+conref="../conrefs.dita#prod/productshortname"></ph> system, see <xref href="cdevcsecure37241.dita#cdevcsecure37241"></xref>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/devguide/rdevcsecure871406.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevcsecure871406.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevcsecure871406.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevcsecure871406.dita Fri Mar 30 08:17:01 2007
@@ -22,14 +22,14 @@
<title>Java 2 security policy file example 1</title>
<prolog></prolog>
<refbody>
-<example> <codeblock><b>/* Grants permission to run <ph conref="devconrefs.dita#prod/productshortname"></ph> and access all */
-/* databases under the <ph conref="devconrefs.dita#prod/productshortname"></ph> system home */
+<example> <codeblock><b>/* Grants permission to run <ph conref="../conrefs.dita#prod/productshortname"></ph> and access all */
+/* databases under the <ph conref="../conrefs.dita#prod/productshortname"></ph> system home */
/* when it is specified by the system property */
-/* <ph conref="devconrefs.dita#prod/productshortname"></ph>.system.home */
+/* <ph conref="../conrefs.dita#prod/productshortname"></ph>.system.home */
-/* Note <ph conref="devconrefs.dita#prod/productshortname"></ph>.system.home must be an absolute pathname */</b>
+/* Note <ph conref="../conrefs.dita#prod/productshortname"></ph>.system.home must be an absolute pathname */</b>
-grant codeBase "file://f:/<ph conref="devconrefs.dita#prod/productlowercase"></ph>/lib/derby.jar" {
+grant codeBase "file://f:/<ph conref="../conrefs.dita#prod/productlowercase"></ph>/lib/derby.jar" {
permission java.lang.RuntimePermission "createClassLoader";
permission java.util.PropertyPermission "derby.*", "read";
Modified: db/derby/docs/trunk/src/devguide/rdevcsecure871422.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevcsecure871422.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevcsecure871422.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevcsecure871422.dita Fri Mar 30 08:17:01 2007
@@ -22,12 +22,12 @@
<title>Java 2 security policy file example 2</title>
<prolog></prolog>
<refbody>
-<example> <codeblock><b>/* Grants permission to run <ph conref="devconrefs.dita#prod/productshortname"></ph> and access all */
-/* databases under the <ph conref="devconrefs.dita#prod/productshortname"></ph> system home */
+<example> <codeblock><b>/* Grants permission to run <ph conref="../conrefs.dita#prod/productshortname"></ph> and access all */
+/* databases under the <ph conref="../conrefs.dita#prod/productshortname"></ph> system home */
/* when it defaults to the current directory */</b>
-grant codeBase "file://f:/<ph conref="devconrefs.dita#prod/productlowercase"></ph>/lib/derby.jar" {
+grant codeBase "file://f:/<ph conref="../conrefs.dita#prod/productlowercase"></ph>/lib/derby.jar" {
permission java.lang.RuntimePermission "createClassLoader";
permission java.util.PropertyPermission "derby.*", "read";
permission java.util.PropertyPermission "user.dir", "read";
Modified: db/derby/docs/trunk/src/devguide/rdevcsecure871439.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevcsecure871439.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevcsecure871439.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevcsecure871439.dita Fri Mar 30 08:17:01 2007
@@ -22,12 +22,12 @@
<title>Java 2 security policy file example 3</title>
<prolog></prolog>
<refbody>
-<example> <codeblock><b>/* Grants permission to run <ph conref="devconrefs.dita#prod/productshortname"></ph> and access a single */
-/* database (salesdb) under the <ph conref="devconrefs.dita#prod/productshortname"></ph> system home */
+<example> <codeblock><b>/* Grants permission to run <ph conref="../conrefs.dita#prod/productshortname"></ph> and access a single */
+/* database (salesdb) under the <ph conref="../conrefs.dita#prod/productshortname"></ph> system home */
-/* Note <ph conref="devconrefs.dita#prod/productshortname"></ph>.system.home must be an absolute pathname */</b>
+/* Note <ph conref="../conrefs.dita#prod/productshortname"></ph>.system.home must be an absolute pathname */</b>
-grant codeBase "file://f:/<ph conref="devconrefs.dita#prod/productlowercase"></ph>/lib/derby.jar" {
+grant codeBase "file://f:/<ph conref="../conrefs.dita#prod/productlowercase"></ph>/lib/derby.jar" {
permission java.lang.RuntimePermission "createClassLoader";
permission java.util.PropertyPermission "derby.*", "read";
Modified: db/derby/docs/trunk/src/devguide/rdevdeploy856948.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevdeploy856948.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevdeploy856948.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevdeploy856948.dita Fri Mar 30 08:17:01 2007
@@ -21,6 +21,6 @@
<prolog>
</prolog>
<refbody>
-<section><p>See the <cite><ph conref="devconrefs.dita#pub/citutilities"></ph></cite> for reference information about
+<section><p>See the <cite><ph conref="../conrefs.dita#pub/citutilities"></ph></cite> for reference information about
the utility and complete syntax.</p></section>
</refbody></reference>
Modified: db/derby/docs/trunk/src/devguide/rdevdvlp22102.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevdvlp22102.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevdvlp22102.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevdvlp22102.dita Fri Mar 30 08:17:01 2007
@@ -29,7 +29,7 @@
<refbody>
<section><p>This information also applies to the client connection URL in
a client/server environment. For reference information about client connection
-URLs, see "java.sql.Connection interface" in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p></section>
+URLs, see "java.sql.Connection interface" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p></section>
<section> <ul>
<li><i>jdbc:derby:db1</i> <p>Open a connection to the database <i>db1</i>. <i>db1</i> is
a directory located in the system directory.</p></li>
@@ -44,10 +44,10 @@
<li><i>jdbc:derby:a:/demo/sample</i> <p>Open a connection to the database
stored in the directory <i>\demo\sample</i> on drive <i>A</i> (usually the
floppy drive) on a Windows system.</p></li>
-<li><i>jdbc:<ph conref="devconrefs.dita#prod/productlowercase"></ph>:c:/databases/salesdb
+<li><i>jdbc:<ph conref="../conrefs.dita#prod/productlowercase"></ph>:c:/databases/salesdb
jdbc:derby:salesdb</i> <p>These two connection URLs connect to the same
database, <i>salesdb</i>, on a Windows platform if the system directory of
-the <ph conref="devconrefs.dita#prod/productshortname"></ph> system is <i>C:\databases</i>.</p></li>
+the <ph conref="../conrefs.dita#prod/productshortname"></ph> system is <i>C:\databases</i>.</p></li>
<li><i>jdbc:derby:support/bugsdb;create=true</i> <p>Create the database <i>support/bugsdb</i> in
the system directory, automatically creating the intermediate directory <i>support</i> if
it does not exist.</p></li>
Modified: db/derby/docs/trunk/src/devguide/rdevdvlp38881.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevdvlp38881.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevdvlp38881.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevdvlp38881.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<reference id="rdevdvlp38881" xml:lang="en-us">
<title>Embedded Derby JDBC database connection URL</title>
-<shortdesc>This is the standard <ph conref="devconrefs.dita#prod/productshortname"></ph> JDBC
+<shortdesc>This is the standard <ph conref="../conrefs.dita#prod/productshortname"></ph> JDBC
connection URL, which you can use for tasks besides connecting to a database.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Database connection URL<indexterm>syntax</indexterm></indexterm>
@@ -33,7 +33,7 @@
<refbody>
<example> <codeblock>jdbc:derby:[subsubprotocol:][<i>databaseName</i>][;<i>attribute</i>=<i>value</i>]*</codeblock></example>
<section><p><i>Subsubprotocol</i>, which is not typically specified, determines
-how <ph conref="devconrefs.dita#prod/productshortname"></ph> looks for a database:
+how <ph conref="../conrefs.dita#prod/productshortname"></ph> looks for a database:
in a directory, in a class path, or in a jar file. Subsubprotocol is one of
the following:</p></section>
<section> <ul>
@@ -55,6 +55,6 @@
<example> <codeblock>DriverManager.getConnection("jdbc:derby:sample");</codeblock></example>
<section><p>You can specify attributes and attribute values to a connection
URL. For detailed reference about attributes and values, see the <cite><ph
-conref="devconrefs.dita#pub/citref"></ph></cite>.</p></section>
+conref="../conrefs.dita#pub/citref"></ph></cite>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/devguide/rdevexudclass.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevexudclass.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevexudclass.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevexudclass.dita Fri Mar 30 08:17:01 2007
@@ -59,7 +59,7 @@
static {
<b> /* load users config file as Java properties
File must be in the same directory where
- <ph conref="devconrefs.dita#prod/productshortname"></ph> gets started.
+ <ph conref="../conrefs.dita#prod/productshortname"></ph> gets started.
(otherwise full path must be specified) */</b>
FileInputStream in = null;
usersConfig = new Properties();
Modified: db/derby/docs/trunk/src/devguide/rdevprocsqle.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevprocsqle.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevprocsqle.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevprocsqle.dita Fri Mar 30 08:17:01 2007
@@ -52,7 +52,7 @@
may wrap another, triggering exception, like an <i>IOException</i>. To inspect
this additional, wrapped error, call the <i>SQLException</i>'s <i>getCause</i> method.
</p></section>
-<section><p>See also "<ph conref="devconrefs.dita#prod/productshortname"></ph> Exception
-Messages and SQL States", in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p></section>
+<section><p>See also "<ph conref="../conrefs.dita#prod/productshortname"></ph> Exception
+Messages and SQL States", in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/devguide/rdevresman79556.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevresman79556.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevresman79556.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevresman79556.dita Fri Mar 30 08:17:01 2007
@@ -52,7 +52,7 @@
A factory for <codeph><i>PooledConnection</i></codeph> objects.</p></li>
<li><i>org.apache.derby.jdbc.EmbeddedXADataSource</i>
and <i>org.apache.derby.jdbc.EmbeddedXADataSource40</i>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph>'s
implementation of a <i>javax.sql.XADataSource</i>.</p></li>
</ul></section>
</refbody>
Modified: db/derby/docs/trunk/src/devguide/rdevtrademderby.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/rdevtrademderby.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/rdevtrademderby.dita (original)
+++ db/derby/docs/trunk/src/devguide/rdevtrademderby.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
<title>Trademarks</title>
<body>
<p>The following terms are trademarks or registered trademarks of other companies
-and have been used in at least one of the documents in the <ph conref="devconrefs.dita#prod/productlongname"></ph> documentation
+and have been used in at least one of the documents in the <ph conref="../conrefs.dita#prod/productlongname"></ph> documentation
library:</p>
<p>Cloudscape, DB2, DB2 Universal Database, DRDA, and IBM are trademarks of
International Business Machines Corporation in the United States, other countries,
Modified: db/derby/docs/trunk/src/devguide/tdevcsecure81850.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevcsecure81850.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevcsecure81850.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevcsecure81850.dita Fri Mar 30 08:17:01 2007
@@ -29,14 +29,14 @@
<step><cmd>Encrypt the database when you create it.</cmd></step>
<step><cmd>Configure all security features as database-level properties.
These properties are stored in the database (which is encrypted). See <cite><ph
-conref="devconrefs.dita#pub/cittuning"></ph></cite>.</cmd></step>
+conref="../conrefs.dita#pub/cittuning"></ph></cite>.</cmd></step>
<step><cmd>Turn on protection for database-level properties so that they cannot
be overridden by system properties by setting the <i>derby.database.propertiesOnly</i> property
to TRUE.</cmd></step>
<step><cmd>To prevent unauthorized users from accessing databases once they
are booted, turn on user authentication for the database and configure user
authorization for the database.</cmd></step>
-<step><cmd>If you are using <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+<step><cmd>If you are using <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
built-in users, configure each user as a database-level property so that user
names and passwords can be encrypted.</cmd></step>
</steps>
Modified: db/derby/docs/trunk/src/devguide/tdevcsecure82556.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevcsecure82556.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevcsecure82556.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevcsecure82556.dita Fri Mar 30 08:17:01 2007
@@ -26,14 +26,14 @@
<taskbody>
<steps>
<step><cmd>Configure security features as system properties. See <cite><ph
-conref="devconrefs.dita#pub/cittuning"></ph></cite>.</cmd></step>
+conref="../conrefs.dita#pub/cittuning"></ph></cite>.</cmd></step>
<step><cmd>Provide administrative-level protection for the <i>derby.properties</i> file
-and <ph conref="devconrefs.dita#prod/productshortname"></ph> databases. For
+and <ph conref="../conrefs.dita#prod/productshortname"></ph> databases. For
example, you can protect these files and directories with operating system
permissions and firewalls.</cmd></step>
<step><cmd>Turn on user authentication for your system. All users must provide
-valid user IDs and passwords to access the <ph conref="devconrefs.dita#prod/productshortname"></ph> system.
-If you are using <ph conref="devconrefs.dita#prod/productshortname"></ph>'s
+valid user IDs and passwords to access the <ph conref="../conrefs.dita#prod/productshortname"></ph> system.
+If you are using <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
built-in users, configure users for the system in the <i>derby.properties</i> file.
Provide the protection for this file.</cmd></step>
<step><cmd>Configure user authorization for sensitive databases in your system.
@@ -44,7 +44,7 @@
of sensitivity.</cmd></step>
<step><cmd>Check and if necessary configure your Derby network security
according to your environment. See the section "Network client security" in the
-<cite><ph conref="devconrefs.dita#pub/citadmin"></ph></cite>.</cmd></step>
+<cite><ph conref="../conrefs.dita#pub/citadmin"></ph></cite>.</cmd></step>
</steps>
<result></result>
</taskbody>
Modified: db/derby/docs/trunk/src/devguide/tdevcsecurenewbootpw.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevcsecurenewbootpw.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevcsecurenewbootpw.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevcsecurenewbootpw.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<task id="tdevcsecurenewbootpw" xml:lang="en-us">
<title>Encrypting databases with a new boot password</title>
-<shortdesc>You can apply a new boot password to a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<shortdesc>You can apply a new boot password to a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
by specifying the <i>newBootPassword</i> attribute on the connection URL when
you boot the database.</shortdesc>
<prolog><metadata>
Modified: db/derby/docs/trunk/src/devguide/tdevcsecurenewextkey.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevcsecurenewextkey.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevcsecurenewextkey.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevcsecurenewextkey.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<task id="tdevcsecurenewextkey" xml:lang="en-us">
<title>Encrypting databases with a new external encryption key</title>
-<shortdesc>You can apply a new external encryption key to a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<shortdesc>You can apply a new external encryption key to a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
by specifying the <i>newEncryptionKey</i> attribute on the connection URL
when you boot the database.</shortdesc>
<prolog><metadata>
Modified: db/derby/docs/trunk/src/devguide/tdevcsecurenewkeyoverview.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevcsecurenewkeyoverview.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevcsecurenewkeyoverview.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevcsecurenewkeyoverview.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<task id="tdevcsecurenewkeyoverview" xml:lang="en-us">
<title>Encrypting databases with a new key</title>
-<shortdesc>You can apply a new encryption key to a <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<shortdesc>You can apply a new encryption key to a <ph conref="../conrefs.dita#prod/productshortname"></ph> database
by specifying a new boot password or a new external key.</shortdesc>
<prolog><metadata>
<keywords><indexterm>encrypting databases<indexterm>new key, overview</indexterm></indexterm>
Modified: db/derby/docs/trunk/src/devguide/tdevcsecureunencrypteddb.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevcsecureunencrypteddb.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevcsecureunencrypteddb.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevcsecureunencrypteddb.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<task id="tdevcsecureunencrypteddb" xml:lang="en-us">
<title>Encrypting an existing unencrypted database</title>
-<shortdesc>You can encrypt an unencrypted <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+<shortdesc>You can encrypt an unencrypted <ph conref="../conrefs.dita#prod/productshortname"></ph> database
by specifying attributes on the connection URL when you boot the database.
The attributes that you specify depend on how you want the database encrypted.</shortdesc>
<prolog><metadata>
Modified: db/derby/docs/trunk/src/devguide/tdevdeploy26887.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevdeploy26887.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevdeploy26887.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevdeploy26887.dita Fri Mar 30 08:17:01 2007
@@ -28,23 +28,23 @@
<taskbody>
<steps>
<step><cmd>Create and populate the database on read-write media.</cmd></step>
-<step><cmd>Commit all transactions and shut down <ph conref="devconrefs.dita#prod/productshortname"></ph> in
-the prescribed manner. If you do not shut down <ph conref="devconrefs.dita#prod/productshortname"></ph> in
-the prescribed manner, <ph conref="devconrefs.dita#prod/productshortname"></ph> will
-need to perform recovery the next time the system boots. <ph conref="devconrefs.dita#prod/productshortname"></ph> cannot
+<step><cmd>Commit all transactions and shut down <ph conref="../conrefs.dita#prod/productshortname"></ph> in
+the prescribed manner. If you do not shut down <ph conref="../conrefs.dita#prod/productshortname"></ph> in
+the prescribed manner, <ph conref="../conrefs.dita#prod/productshortname"></ph> will
+need to perform recovery the next time the system boots. <ph conref="../conrefs.dita#prod/productshortname"></ph> cannot
perform recovery on read-only media.</cmd></step>
<step><cmd>Delete the <i>tmp</i> directory if one was created within your
-database directory. If you include this directory, <ph conref="devconrefs.dita#prod/productshortname"></ph> will
+database directory. If you include this directory, <ph conref="../conrefs.dita#prod/productshortname"></ph> will
attempt to delete it and will return errors when attempting to boot a database
on read-only media.</cmd></step>
<step><cmd>For the read-only database, set the property <i>derby.storage.tempDirectory</i> to
-a writable location.</cmd><info><ph conref="devconrefs.dita#prod/productshortname"></ph> needs
+a writable location.</cmd><info><ph conref="../conrefs.dita#prod/productshortname"></ph> needs
to write to temporary files for large sorts required by such SQL statements
as ORDER BY, UNION, DISTINCT, and GROUP BY. For more information about this
-property, see <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>.<codeblock>derby.storage.tempDirectory=c:/temp/mytemp</codeblock></info>
+property, see <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite>.<codeblock>derby.storage.tempDirectory=c:/temp/mytemp</codeblock></info>
</step>
<step><cmd>Configure the database to send error messages to a writable file
-or to an output stream.</cmd><info>For information, see <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>.<codeblock>derby.stream.error.file=c:/temp/mylog.LOG</codeblock
+or to an output stream.</cmd><info>For information, see <cite><ph conref="../conrefs.dita#pub/cittuning"></ph></cite>.<codeblock>derby.stream.error.file=c:/temp/mylog.LOG</codeblock
></info></step>
</steps>
<result>Be sure to set these properties so that they are deployed with the
Modified: db/derby/docs/trunk/src/devguide/tdevdeploy33704.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevdeploy33704.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevdeploy33704.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevdeploy33704.dita Fri Mar 30 08:17:01 2007
@@ -20,8 +20,8 @@
-->
<task id="tdevdeploy33704" xml:lang="en-us">
<title>Transferring read-only databases to archive (jar or zip) files</title>
-<shortdesc>Once a database has been created in <ph conref="devconrefs.dita#prod/productshortname"></ph>,
-it can be stored in a jar or zip file and continue to be accessed by <ph conref="devconrefs.dita#prod/productshortname"></ph> in
+<shortdesc>Once a database has been created in <ph conref="../conrefs.dita#prod/productshortname"></ph>,
+it can be stored in a jar or zip file and continue to be accessed by <ph conref="../conrefs.dita#prod/productshortname"></ph> in
read-only mode.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Zip files<indexterm>databases in</indexterm></indexterm>
@@ -32,11 +32,11 @@
<taskbody>
<context> <p>This allows a read-only database to be distributed as a single
file instead of as multiple files within a directory and to be compressed.
-In fact, a jar or zip file can contain any number of <ph conref="devconrefs.dita#prod/productshortname"></ph> databases
-and can also contain other information not related to <ph conref="devconrefs.dita#prod/productshortname"></ph>,
+In fact, a jar or zip file can contain any number of <ph conref="../conrefs.dita#prod/productshortname"></ph> databases
+and can also contain other information not related to <ph conref="../conrefs.dita#prod/productshortname"></ph>,
such as application data or code.</p><p>You cannot store the <i>derby.properties</i> file
in a jar or zip file.</p><p>To create a jar or zip file containing one or
-more <ph conref="devconrefs.dita#prod/productshortname"></ph> databases: <ol>
+more <ph conref="../conrefs.dita#prod/productshortname"></ph> databases: <ol>
<li>Create a database for use on read-only media.</li>
<li>From the directory that contains the database folder, archive the database
directory and its contents. For example, for the database<i> sales</i> that
Modified: db/derby/docs/trunk/src/devguide/tdevdeploy39856.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevdeploy39856.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevdeploy39856.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevdeploy39856.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<task id="tdevdeploy39856" xml:lang="en-us">
<title>Accessing databases within a jar file using the classpath</title>
-<shortdesc>Once an archive containing one or more <ph conref="devconrefs.dita#prod/productshortname"></ph> databases
+<shortdesc>Once an archive containing one or more <ph conref="../conrefs.dita#prod/productshortname"></ph> databases
has been created it can be placed in the classpath. This allows access to
a database from within an application without the application's knowing the
path of the archive.</shortdesc>
@@ -35,7 +35,7 @@
in a zip or jar file in the classpath:</p></context>
<steps>
<step><cmd>Set the classpath to include the jar or zip file before starting
-up <ph conref="devconrefs.dita#prod/productshortname"></ph>:</cmd><info><codeblock>CLASSPATH="C:\dbs.jar;%CLASSPATH%"</codeblock></info>
+up <ph conref="../conrefs.dita#prod/productshortname"></ph>:</cmd><info><codeblock>CLASSPATH="C:\dbs.jar;%CLASSPATH%"</codeblock></info>
</step>
<step><cmd>Connect to a database within the jar or zip file with one of the
following connection URLs:</cmd><info><codeblock><b>Standard syntax:</b>
Modified: db/derby/docs/trunk/src/devguide/tdevdvlp20349.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevdvlp20349.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevdvlp20349.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevdvlp20349.dita Fri Mar 30 08:17:01 2007
@@ -21,34 +21,34 @@
<task id="tdevdvlp20349" xml:lang="en-us">
<title>Shutting down the system</title>
<shortdesc>In an embedded environment, when an application shuts down, it
-should first shut down <ph conref="devconrefs.dita#prod/productshortname"></ph>.</shortdesc>
+should first shut down <ph conref="../conrefs.dita#prod/productshortname"></ph>.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Shutting down the system</indexterm></keywords>
</metadata></prolog>
<taskbody>
-<context> <p>If the application that started the embedded <ph conref="devconrefs.dita#prod/productshortname"></ph> quits
-but leaves the JVM running, <ph conref="devconrefs.dita#prod/productshortname"></ph> continues
+<context> <p>If the application that started the embedded <ph conref="../conrefs.dita#prod/productshortname"></ph> quits
+but leaves the JVM running, <ph conref="../conrefs.dita#prod/productshortname"></ph> continues
to run and is available for database connections.</p><p>In an embedded system,
-the application shuts down the <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+the application shuts down the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
by issuing the following JDBC call:</p><codeblock>DriverManager.getConnection("jdbc:derby:;shutdown=true");</codeblock><p>Shutdown
-commands always raise <i>SQLExceptions</i>.</p><p>When a <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+commands always raise <i>SQLExceptions</i>.</p><p>When a <ph conref="../conrefs.dita#prod/productshortname"></ph> system
shuts down, a message goes to the error log:</p><codeblock>Sat Jan 10 14:31:54 PDT 2005:
Shutting down instance 80000001-00d0-8bdf-d115-000a0a0b2d00</codeblock><p>Typically,
-an application using an embedded <ph conref="devconrefs.dita#prod/productshortname"></ph> engine
-shuts down <ph conref="devconrefs.dita#prod/productshortname"></ph> just before
-shutting itself down. However, an application can shut down <ph conref="devconrefs.dita#prod/productshortname"></ph> and
-later restart it in the same JVM session. To restart <ph conref="devconrefs.dita#prod/productshortname"></ph> successfully,
+an application using an embedded <ph conref="../conrefs.dita#prod/productshortname"></ph> engine
+shuts down <ph conref="../conrefs.dita#prod/productshortname"></ph> just before
+shutting itself down. However, an application can shut down <ph conref="../conrefs.dita#prod/productshortname"></ph> and
+later restart it in the same JVM session. To restart <ph conref="../conrefs.dita#prod/productshortname"></ph> successfully,
the JVM needs to unload <i>org.apache.derby.jdbc.EmbeddedDriver</i>, so that
-it can reload it when it restarts <ph conref="devconrefs.dita#prod/productshortname"></ph>.
-(Loading the local driver starts <ph conref="devconrefs.dita#prod/productshortname"></ph>.) </p><p>You
+it can reload it when it restarts <ph conref="../conrefs.dita#prod/productshortname"></ph>.
+(Loading the local driver starts <ph conref="../conrefs.dita#prod/productshortname"></ph>.) </p><p>You
cannot explicitly request that the JVM unload a class, but you can ensure
that the <i>EmbeddedDriver</i> class is unloaded by using a <codeph><i>System.gc()</i></codeph> to
force it to garbage collect classes that are no longer needed. Running with <codeph><i>-nogc</i></codeph> or <codeph><i>-noclassgc</i></codeph> definitely <i
>prevents</i> the class from being unloaded and makes you unable to restart <ph
-conref="devconrefs.dita#prod/productshortname"></ph> in the same JVM. </p><p>It
+conref="../conrefs.dita#prod/productshortname"></ph> in the same JVM. </p><p>It
is also possible to shut down a single database instead of the entire <ph
-conref="devconrefs.dita#prod/productshortname"></ph> system. See <xref href="tdevdvlp40464.dita#tdevdvlp40464"></xref>.
-You can reboot a database in the same <ph conref="devconrefs.dita#prod/productshortname"></ph> session
+conref="../conrefs.dita#prod/productshortname"></ph> system. See <xref href="tdevdvlp40464.dita#tdevdvlp40464"></xref>.
+You can reboot a database in the same <ph conref="../conrefs.dita#prod/productshortname"></ph> session
after shutting it down.</p></context>
</taskbody>
</task>
Modified: db/derby/docs/trunk/src/devguide/tdevdvlp38381.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevdvlp38381.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevdvlp38381.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevdvlp38381.dita Fri Mar 30 08:17:01 2007
@@ -20,10 +20,10 @@
-->
<task id="tdevdvlp38381" xml:lang="en-us">
<title>Starting Derby as an embedded database</title>
-<shortdesc>To start <ph conref="devconrefs.dita#prod/productshortname"></ph>,
-you start the <ph conref="devconrefs.dita#prod/productshortname"></ph> JDBC
-driver. Starting the <ph conref="devconrefs.dita#prod/productshortname"></ph> driver
-starts up the complete <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<shortdesc>To start <ph conref="../conrefs.dita#prod/productshortname"></ph>,
+you start the <ph conref="../conrefs.dita#prod/productshortname"></ph> JDBC
+driver. Starting the <ph conref="../conrefs.dita#prod/productshortname"></ph> driver
+starts up the complete <ph conref="../conrefs.dita#prod/productshortname"></ph> system
within the current JVM.</shortdesc>
<prolog><metadata>
<keywords><indexterm>Starting Derby<indexterm>embedded mode</indexterm></indexterm>
@@ -45,9 +45,9 @@
need to explicitlty load the EmbeddedDriver. In that environment, the
driver loads automatically and the engine starts when your application
requests its first Connection.</li>
-</ul><p>For more details, see "java.sql.Driver interface" in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>.</p><p>Once
-the <ph conref="devconrefs.dita#prod/productshortname"></ph> JDBC driver class
-has been loaded, you can connect to any <ph conref="devconrefs.dita#prod/productshortname"></ph> database
+</ul><p>For more details, see "java.sql.Driver interface" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p><p>Once
+the <ph conref="../conrefs.dita#prod/productshortname"></ph> JDBC driver class
+has been loaded, you can connect to any <ph conref="../conrefs.dita#prod/productshortname"></ph> database
by passing the embedded connection URL with the appropriate attributes to
the <i>DriverManager.getConnection</i> method.</p><p>For example:<codeblock>Connection conn = DriverManager.getConnection("jdbc:derby:sample");</codeblock
></p></context>
Modified: db/derby/docs/trunk/src/devguide/tdevdvlp39090.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevdvlp39090.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevdvlp39090.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevdvlp39090.dita Fri Mar 30 08:17:01 2007
@@ -28,12 +28,12 @@
</keywords>
</metadata></prolog>
<taskbody>
-<context> <p><ph conref="devconrefs.dita#prod/productshortname"></ph> creates
+<context> <p><ph conref="../conrefs.dita#prod/productshortname"></ph> creates
a new database inside a new subdirectory in the system directory. This system
directory has the same name as the new database. If you specify a partial
path, it is relative to the system directory. You can also specify an absolute
path.</p><codeblock>jdbc:derby:<i>databaseName</i>;<ph>create=true</ph></codeblock><p>For
more details about <i>create=true</i>, see <i>"create=true"</i> in the <cite><ph
-conref="devconrefs.dita#pub/citref"></ph></cite>.</p></context>
+conref="../conrefs.dita#pub/citref"></ph></cite>.</p></context>
</taskbody>
</task>
Modified: db/derby/docs/trunk/src/devguide/tdevdvlp40140.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevdvlp40140.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevdvlp40140.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevdvlp40140.dita Fri Mar 30 08:17:01 2007
@@ -40,7 +40,7 @@
encryptionKey=c566bab9ee8b62a5ddb4d9229224c678 </codeblock><p>If the algorithm
that was used when the database was created is not the default algorithm,
you must also specify the <i>encryptionAlgorithm</i> attribute. The default
-encryption algorithm used by <ph conref="devconrefs.dita#prod/productshortname"></ph> is
+encryption algorithm used by <ph conref="../conrefs.dita#prod/productshortname"></ph> is
DES/CBC/NoPadding.</p></choice>
</choices>
</step>
Modified: db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevdvlp40464.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<task id="tdevdvlp40464" xml:lang="en-us">
<title>Shutting down Derby or an individual database</title>
-<shortdesc>Applications in an embedded environment shut down the <ph conref="devconrefs.dita#prod/productshortname"></ph> system
+<shortdesc>Applications in an embedded environment shut down the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
by specifying the <i>shutdown=true</i> attribute in the connection URL. To
shut down the system, you do not specify a database name, and you must not
specify any other attribute.</shortdesc>
@@ -32,7 +32,7 @@
</metadata></prolog>
<taskbody>
<context> <codeblock>jdbc:derby:;<ph>shutdown=true</ph></codeblock><p>A successful
-shutdown always results in an <i>SQLException</i> to indicate that <ph conref="devconrefs.dita#prod/productshortname"></ph> has
+shutdown always results in an <i>SQLException</i> to indicate that <ph conref="../conrefs.dita#prod/productshortname"></ph> has
shut down and that there is no other exception.</p><p>You can also shut down
an individual database if you specify the <i>databaseName</i>. You can shut
down the database of the current connection if you specify the default connection
Modified: db/derby/docs/trunk/src/devguide/tdevpreupgrade.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevpreupgrade.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevpreupgrade.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevpreupgrade.dita Fri Mar 30 08:17:01 2007
@@ -20,7 +20,7 @@
-->
<task id="tdevpreupgrade" xml:lang="en-us">
<title>Preparing to upgrade</title>
-<shortdesc>Upgrading your database occurs the first time the new <ph conref="devconrefs.dita#prod/productshortname"></ph> software
+<shortdesc>Upgrading your database occurs the first time the new <ph conref="../conrefs.dita#prod/productshortname"></ph> software
connects to the old database.</shortdesc>
<prolog><metadata>
<keywords><indexterm>upgrading Derby<indexterm>prerequisites</indexterm></indexterm>
@@ -29,17 +29,17 @@
<taskbody>
<context> <p>Before you connect to the database using the new software:</p></context>
<steps>
-<step><cmd>Back up your database to a safe location using <ph conref="devconrefs.dita#prod/productshortname"></ph> online/offline
+<step><cmd>Back up your database to a safe location using <ph conref="../conrefs.dita#prod/productshortname"></ph> online/offline
backup procedures.</cmd><info>For more information on backup, see the <ph
-conref="devconrefs.dita#pub/citadmin"></ph>.</info></step>
+conref="../conrefs.dita#pub/citadmin"></ph>.</info></step>
<step><cmd>Update your CLASSPATH with the latest jar files.</cmd></step>
-<step><cmd>Make sure that there are no older versions of the <ph conref="devconrefs.dita#prod/productshortname"></ph> jar
-files in your CLASSPATH. You can determine if you have multiple versions of <ph conref="devconrefs.dita#prod/productshortname"></ph> in your CLASSPATH by using the sysinfo tool.</cmd>
+<step><cmd>Make sure that there are no older versions of the <ph conref="../conrefs.dita#prod/productshortname"></ph> jar
+files in your CLASSPATH. You can determine if you have multiple versions of <ph conref="../conrefs.dita#prod/productshortname"></ph> in your CLASSPATH by using the sysinfo tool.</cmd>
<stepxmp>To use the <codeph>sysinfo</codeph> tool,
execute the following command:<codeblock>java org.apache.derby.tools.sysinfo</codeblock>The <codeph>sysinfo</codeph> tool
-uses information found in the <ph conref="devconrefs.dita#prod/productshortname"></ph> jar
-files to determine the version of any <ph conref="devconrefs.dita#prod/productshortname"></ph> jar in your CLASSPATH. Be sure that you have only one version of
-the <ph conref="devconrefs.dita#prod/productshortname"></ph> jar files specified
+uses information found in the <ph conref="../conrefs.dita#prod/productshortname"></ph> jar
+files to determine the version of any <ph conref="../conrefs.dita#prod/productshortname"></ph> jar in your CLASSPATH. Be sure that you have only one version of
+the <ph conref="../conrefs.dita#prod/productshortname"></ph> jar files specified
in your CLASSPATH.</stepxmp></step>
</steps>
</taskbody>
Modified: db/derby/docs/trunk/src/devguide/tdevupgradedb.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevupgradedb.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevupgradedb.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevupgradedb.dita Fri Mar 30 08:17:01 2007
@@ -21,7 +21,7 @@
<task id="tdevupgradedb" xml:lang="en-us">
<title>Upgrading a database</title>
<shortdesc>To upgrade a database, you must explicitly request an upgrade the
-first time you connect to the database with the new version of <ph conref="devconrefs.dita#prod/productshortname"></ph>.</shortdesc>
+first time you connect to the database with the new version of <ph conref="../conrefs.dita#prod/productshortname"></ph>.</shortdesc>
<prolog><metadata>
<keywords><indexterm>upgrading Derby<indexterm>full upgrade</indexterm></indexterm>
<indexterm>upgrading Derby<indexterm>soft upgrade</indexterm></indexterm>
@@ -32,18 +32,18 @@
<prereq>Ensure that you <xref href="tdevpreupgrade.dita">complete the prerequisite
steps</xref> before you upgrade:<ul>
<li>Back up your database before you upgrade.</li>
-<li>Ensure that only the new <ph conref="devconrefs.dita#prod/productshortname"></ph> jar
+<li>Ensure that only the new <ph conref="../conrefs.dita#prod/productshortname"></ph> jar
files are in your CLASSPATH.</li>
</ul></prereq>
<context> <p>When you upgrade the database, you can perform a full upgrade
or soft upgrade:<ul>
-<li>A full upgrade is a complete upgrade of the <ph conref="devconrefs.dita#prod/productshortname"></ph> database.
+<li>A full upgrade is a complete upgrade of the <ph conref="../conrefs.dita#prod/productshortname"></ph> database.
When you perform a full upgrade, you cannot connect to the database with an
-older version of <ph conref="devconrefs.dita#prod/productshortname"></ph> and
+older version of <ph conref="../conrefs.dita#prod/productshortname"></ph> and
you cannot revert back to the previous version. </li>
-<li>A soft upgrade allows you to run a newer version of <ph conref="devconrefs.dita#prod/productshortname"></ph> against
+<li>A soft upgrade allows you to run a newer version of <ph conref="../conrefs.dita#prod/productshortname"></ph> against
an existing database without having to fully upgrade the database. This means
-that you can continue to run an older version of <ph conref="devconrefs.dita#prod/productshortname"></ph> against
+that you can continue to run an older version of <ph conref="../conrefs.dita#prod/productshortname"></ph> against
the database. However, if you perform a soft upgrade, certain features will
not be available to you until you perform a full upgrade.</li>
</ul></p></context>
Modified: db/derby/docs/trunk/src/devguide/tdevupgradesoft.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/tdevupgradesoft.dita?view=diff&rev=524118&r1=524117&r2=524118
==============================================================================
--- db/derby/docs/trunk/src/devguide/tdevupgradesoft.dita (original)
+++ db/derby/docs/trunk/src/devguide/tdevupgradesoft.dita Fri Mar 30 08:17:01 2007
@@ -20,9 +20,9 @@
-->
<task id="tdevupgradesoft" xml:lang="en-us">
<title>Soft upgrade limitations</title>
-<shortdesc>Soft upgrade allows you to run a newer version of <ph conref="devconrefs.dita#prod/productshortname"></ph> against
+<shortdesc>Soft upgrade allows you to run a newer version of <ph conref="../conrefs.dita#prod/productshortname"></ph> against
an existing database without having to fully upgrade the database. This means
-that you can continue to run an older version of <ph conref="devconrefs.dita#prod/productshortname"></ph> against
+that you can continue to run an older version of <ph conref="../conrefs.dita#prod/productshortname"></ph> against
the database.</shortdesc>
<prolog><metadata>
<keywords><indexterm>soft upgrade<indexterm>limitations</indexterm></indexterm>
@@ -31,8 +31,8 @@
</metadata></prolog>
<taskbody>
<context> <p>If you perform a soft upgrade, you will not be able to perform
-certain functions that are not available in older versions of <ph conref="devconrefs.dita#prod/productshortname"></ph>.
-For example, the following <ph conref="devconrefs.dita#prod/productshortname"></ph> Version
+certain functions that are not available in older versions of <ph conref="../conrefs.dita#prod/productshortname"></ph>.
+For example, the following <ph conref="../conrefs.dita#prod/productshortname"></ph> Version
10.2 features cannot be used in a database that has been soft upgraded from
10.0: </p> <ul>
<li>SYNONYMS</li>
@@ -45,10 +45,10 @@
<li>Online backup procedures SYSCS_UTIL.SYSCS_BACKUP_DATABASE_NOWAIT and
SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE_NOWAIT.</li>
<li>The encryption or re-encryption of a database with a new phrase/key.</li>
-</ul> <p> Other new features in <ph conref="devconrefs.dita#prod/productshortname"></ph> that
+</ul> <p> Other new features in <ph conref="../conrefs.dita#prod/productshortname"></ph> that
do not affect database structure, such as using timestamp arithmetic, are
allowed in a soft upgraded database.</p><p>To perform a soft upgrade on a
-database created using an earlier version of <ph conref="devconrefs.dita#prod/productshortname"></ph>:</p></context>
+database created using an earlier version of <ph conref="../conrefs.dita#prod/productshortname"></ph>:</p></context>
<steps>
<step><cmd> Simply connect to the database, as shown in the following example:</cmd>
<info><codeblock>connect 'jdbc:derby:sample'</codeblock>In this example, the