db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From arm...@apache.org
Subject cvs commit: jakarta-ojb/xdocs platforms.xml query.xml repository.xml
Date Sat, 21 Dec 2002 18:57:19 GMT
arminw      2002/12/21 10:57:19

  Modified:    xdocs    platforms.xml query.xml repository.xml
  Log:
  improve document view
  
  Revision  Changes    Path
  1.6       +53 -49    jakarta-ojb/xdocs/platforms.xml
  
  Index: platforms.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-ojb/xdocs/platforms.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- platforms.xml	6 Oct 2002 12:57:07 -0000	1.5
  +++ platforms.xml	21 Dec 2002 18:57:19 -0000	1.6
  @@ -145,16 +145,16 @@
   </table>
   
   <p>
  -	OJB uses <a href="http://jakarta.apache.org/turbine/torque/">Torque</a> 
  +	OJB uses <a href="http://jakarta.apache.org/turbine/torque/">Torque</a>
   	to create all required tables and data.
   	Thus there is no SQL DDL file, but an XML file describing the
   	tables in format readable by Torque.
   
  -	The Torque DDL information for the internal tables resides in the 
  +	The Torque DDL information for the internal tables resides in the
   	file <code>src/schema/ojbcore-schema.xml</code>.
   </p>
   <p>
  -	The o/r mappings for these tables are contained in the file 
  +	The o/r mappings for these tables are contained in the file
   	<code>repository_internal.xml</code>.
   </p>
   
  @@ -166,17 +166,17 @@
   	Thus you will have to provide several more tables, filled with the proper
   	testdata.
   </p>
  -<p>	
  -	The DDL information for these tables resides in the 
  +<p>
  +	The DDL information for these tables resides in the
   	file <code>src/schema/ojbtest-schema.xml</code>.
   </p>
  -<p>	
  -	The testdata is defined in the 
  -	file <code>src/schema/ojbtest-data.xml</code>.	
  +<p>
  +	The testdata is defined in the
  +	file <code>src/schema/ojbtest-data.xml</code>.
   </p>
   <p>
  -	The o/r mappings for these tables are contained in the file 
  -	<code>repository_junit.xml</code>.	
  +	The o/r mappings for these tables are contained in the file
  +	<code>repository_junit.xml</code>.
   </p>
   </subsection>
   
  @@ -186,17 +186,17 @@
   	against your target database
   	you will have to provide one extra table.
   </p>
  -<p>	
  -	The DDL information for this table also resides in the 
  +<p>
  +	The DDL information for this table also resides in the
   	file <code>src/schema/ojbtest-schema.xml</code>.
   </p>
  -<p>	
  -	The testdata is also defined in the 
  -	file <code>src/schema/ojbtest-data.xml</code>.	
  +<p>
  +	The testdata is also defined in the
  +	file <code>src/schema/ojbtest-data.xml</code>.
   </p>
   <p>
  -	The o/r mappings for this table is contained in the file 
  -	<code>repository_user.xml</code>.	
  +	The o/r mappings for this table is contained in the file
  +	<code>repository_user.xml</code>.
   </p>
   </subsection>
   
  @@ -204,7 +204,7 @@
   <section name="the setup process">
   <p>
   	OJB provides a setup routine to generate the target database and to fill it
  -	with the required testdata. 
  +	with the required testdata.
   	This routine is based on Torque scripts and is driven from the build.xml file.
   	This section describes how to use it.
   </p>
  @@ -215,10 +215,12 @@
   	in the file build.properties.
   	You can choose one out of the predefined profiles:
   	<source>
  -# With the 'profile' property you can choose the RDBMS platform OJB is using
  -# implemented profiles:
  +# With the 'profile' property you can choose
  +# the RDBMS platform OJB is using implemented profiles:
   profile=hsqldb
   #profile=mssqldb
  +#profile=mssqldb-JNet
  +#profile=mssqldb-Opta2000
   #profile=mysql
   #profile=db2
   #profile=oracle
  @@ -227,16 +229,16 @@
   #profile=informix
   #profile=sybase
   #profile=sapdb
  -	</source> 
  +	</source>
   </p>
   <p>
  -	The profile switch activated in <code>build.properties</code> is used to 
  +	The profile switch activated in <code>build.properties</code> is used to
   	select a profile file from the <code>profile</code> directory.
   	<br/>
  -	If you set <code>profile=db2</code>, then the file <code>profile/db2.profile</code>

  +	If you set <code>profile=db2</code>, then the file <code>profile/db2.profile</code>
   	is selected.
   	<br/>
  -	This file is used by the Torque scripts to set platform specific 
  +	This file is used by the Torque scripts to set platform specific
   	properties and to perform platform specific SQL operations.
   </p>
   
  @@ -244,23 +246,23 @@
   
   <subsection name="editing the profile to point to your target db">
   <p>
  -	The platform specific file <code>profile/xxx.profile</code> 
  +	The platform specific file <code>profile/xxx.profile</code>
   	contains lots of information used by Torque.
   	You can ignore most of it.
   	The only important part in this file is the section where
   	the url to the target db is assembled:
   </p>
   <source>
  -# -------------------------------------------------------------------
  +# ----------------------------------------------------------------
   #
   #  D A T A B A S E  S E T T I N G S
   #
  -# -------------------------------------------------------------------
  -# JDBC connection settings. This is used by the JDBCToXML task that
  -# will create an XML database schema from JDBC metadata. These
  -# settings are also used by the SQL Ant task to initialize your
  -# Turbine system with the generated SQL.
  -# -------------------------------------------------------------------
  +# ----------------------------------------------------------------
  +# JDBC connection settings. This is used by the JDBCToXML task
  +# that will create an XML database schema from JDBC metadata.
  +# These settings are also used by the SQL Ant task to initialize
  +# your Turbine system with the generated SQL.
  +# ----------------------------------------------------------------
   
   dbmsName = Db2
   jdbcLevel = 1.0
  @@ -279,14 +281,14 @@
   
   <p>
   	These settings result in a database URL <code>jdbc:db2:OJB</code>.
  -	If your production database is registered with the name 
  -	<code>MY_PRODUCTION_DB</code> you have to edit the entry 
  +	If your production database is registered with the name
  +	<code>MY_PRODUCTION_DB</code> you have to edit the entry
   	<code>urlDBalias</code> to:<br/>
   	<code>urlDbalias = MY_PRODUCTION_DB</code>.
   </p>
   <p>
   	In this section you can also set application user name and password.
  -	You can also enter a different jdbc driver class, to activate a different 
  +	You can also enter a different jdbc driver class, to activate a different
   	driver.
   </p>
   <p>
  @@ -302,7 +304,7 @@
   <subsection name="executing the build script">
   <p>
   	Now everything should be prepared to launch the setup routine.
  -	This routine can be invoked by calling 
  +	This routine can be invoked by calling
   	<B><code>build[.sh] prepare-testdb</code></B>.
   </p>
   <p>
  @@ -343,7 +345,7 @@
   	You can touch these scripts to match your database specifics and
   	execute them manually against your platform.
   </p>
  -	
  +
   </subsection>
   
   <subsection name="verifying the installation">
  @@ -353,30 +355,32 @@
   </p>
   <p>
   	Execute <b><code>build[.sh] junit</code></b> to see if everything
works as expected.
  -	If you did not manage to set up the target database with the  
  +	If you did not manage to set up the target database with the
   	<code>build[.sh] prepare-testdb</code> you can use <br/>
   	<b><code>build[.sh] junit-no-compile-no-prepare</code></b> to
   	run the testsuite without generation of the test database.
   </p>
  -<p>	
  -	After running the regression tests 
  +<p>
  +	After running the regression tests
   	you should see a console output as follows:
   </p>
   <source>
   ...
  -
   junit-no-compile-no-prepare:
       [junit] Running org.apache.ojb.broker.AllTests
  -    [junit] Tests run: 99, Failures: 0, Errors: 0, Time elapsed: 8,337 sec
  +    [junit] Tests run: 99, Failures: 0, Errors: 0,
  +    Time elapsed: 8,337 sec
       [junit] Running org.apache.ojb.odmg.AllTests
  -    [junit] [BOOT] INFO: OJB.properties: file:/home/tom/workspace/jakarta-ojb/target/test/ojb/OJB.properties
  -    [junit] Tests run: 118, Failures: 0, Errors: 0, Time elapsed: 12,506 sec
  +    [junit] [BOOT] INFO: OJB.properties: file:
  +    /home/tom/workspace/jakarta-ojb/target/test/ojb/OJB.properties
  +    [junit] Tests run: 118, Failures: 0, Errors: 0,
  +    Time elapsed: 12,506 sec
       [junit] Running org.apache.ojb.soda.AllTests
  -    [junit] [BOOT] INFO: OJB.properties: file:/home/tom/workspace/jakarta-ojb/target/test/ojb/OJB.properties
  -    [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 6,391 sec
  -
  +    [junit] [BOOT] INFO: OJB.properties: file:
  +    /home/tom/workspace/jakarta-ojb/target/test/ojb/OJB.properties
  +    [junit] Tests run: 3, Failures: 0, Errors: 0,
  +    Time elapsed: 6,391 sec
   ...
  -
   BUILD SUCESSFUL
   </source>
   
  @@ -399,7 +403,7 @@
   			be problems with your platform.
   			<br/>
   			In such a case please check again if you followed all the above
  -			steps. If you still have problems you might post a request to 
  +			steps. If you still have problems you might post a request to
   			the OJB user mailinglist.
   		</li>
   
  
  
  
  1.11      +6 -4      jakarta-ojb/xdocs/query.xml
  
  Index: query.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-ojb/xdocs/query.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- query.xml	21 Dec 2002 16:17:34 -0000	1.10
  +++ query.xml	21 Dec 2002 18:57:19 -0000	1.11
  @@ -110,8 +110,8 @@
   the limit is set to 3 for the following sample:
   
   <source><![CDATA[
  -SELECT ... FROM Artikel A0 WHERE A0.Kategorie_Nr IN ( ? , ? , ? ) OR
  -A0.Kategorie_Nr IN ( ? , ? ) ORDER BY 7 DESC
  +SELECT ... FROM Artikel A0 WHERE A0.Kategorie_Nr IN ( ? , ? , ? )
  +OR A0.Kategorie_Nr IN ( ? , ? ) ORDER BY 7 DESC
   ]]></source>
   <br/>
   
  @@ -184,7 +184,8 @@
   in the ORDER BY clause:
   
   <source><![CDATA[
  -SELECT A0.ID,A0.FIRSTNAME,A0.LASTNAME FROM PERSON A0 ORDER BY 1 DESC,3
  +SELECT A0.ID,A0.FIRSTNAME,A0.LASTNAME FROM
  +PERSON A0 ORDER BY 1 DESC, 3
   ]]></source>
   
   <br/>
  @@ -278,7 +279,8 @@
   <br/>
   The first query reads all matching ProductGroups:
   <source><![CDATA[
  -SELECT ... FROM Kategorien A0 WHERE A0.Kategorie_Nr <= ? ORDER BY 3 DESC
  +SELECT ... FROM Kategorien A0 WHERE
  +A0.Kategorie_Nr <= ? ORDER BY 3 DESC
   ]]></source>
   
   The second query retrieves Articles belonging to the ProductGroups read by the first query:
  
  
  
  1.10      +141 -132  jakarta-ojb/xdocs/repository.xml
  
  Index: repository.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-ojb/xdocs/repository.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- repository.xml	29 Sep 2002 21:14:27 -0000	1.9
  +++ repository.xml	21 Dec 2002 18:57:19 -0000	1.10
  @@ -11,10 +11,10 @@
   
   <section name="repository syntax">
   <p>
  -	The syntax of the OJB repository xml files is defined by the 
  +	The syntax of the OJB repository xml files is defined by the
   	<code>repository.dtd</code>.
   	<br/>
  -	The <a href="repository.dtd.txt">repository.dtd can be found here</a>. 
  +	The <a href="repository.dtd.txt">repository.dtd can be found here</a>.
   </p>
   
   <p>
  @@ -22,8 +22,8 @@
   	<ol>
   		<li>
   			<a href="repository.xml.txt">the repository.xml</a>.
  -			This file contains the global jdbc-connection-descriptor 
  -			and includes the following three files.		
  +			This file contains the global jdbc-connection-descriptor
  +			and includes the following three files.
   		</li>
   		<li>
   			<a href="repository_internal.xml.txt">the repository_internal.xml</a>.
  @@ -41,7 +41,7 @@
   			This file contains mappings for the tutorial applications
   			and may be used to hold further user defined class mappings.
   		</li>
  -		
  +
   	</ol>
   </p>
   
  @@ -62,7 +62,8 @@
   	persistent classes.
   </p>
   <source><![CDATA[
  -<!ELEMENT descriptor-repository (jdbc-connection-descriptor, class-descriptor+)>
  +<!ELEMENT descriptor-repository (
  +            jdbc-connection-descriptor, class-descriptor+)>
   ]]></source>
   
   <p>
  @@ -75,8 +76,9 @@
   <source><![CDATA[
   <!ATTLIST descriptor-repository
   	version (0.9.6) #REQUIRED
  -	isolation-level (read-uncommitted | read-committed | repeatable-read |
  -	                 serializable | optimistic) "read-uncommitted"
  +	isolation-level (read-uncommitted | read-committed |
  +                    repeatable-read | serializable |
  +                    optimistic) "read-uncommitted"
   >
   ]]></source>
   
  @@ -89,15 +91,15 @@
   	connection.
   </p>
   <p>
  -	A connection-pool element may be used to define connection pool 
  +	A connection-pool element may be used to define connection pool
   	properties for the specified JDBC connection.
   </p>
   <source><![CDATA[
   <!ELEMENT jdbc-connection-descriptor (connection-pool?)>
   ]]></source>
   <p>
  -	The platform attribute is used to define the specific RDBMS Platform.
  -	This attribute corresponds to a
  +	The platform attribute is used to define the specific
  +    RDBMS Platform. This attribute corresponds to a
   	org.apache.ojb.broker.platforms.PlatformXXXImpl class.
   <br/><br/>
   	The jdbc-level attribute is used to specify the Jdbc compliance
  @@ -142,61 +144,67 @@
   <!ELEMENT connection-pool EMPTY>
   ]]></source>
   </p>
  +
   <p>
  -	maxActive:
  -	maximum number of connections that can be borrowed from the
  -	pool at one time. When non-positive, there is no limit.
  -</p>
  -<p>	
  -	maxIdle:
  -	controls the maximum number of connections that can sit idle in the
  -	pool at any time. When non-positive, there is no limit
  -</p>
  -<p>	
  -	maxWait:
  -	max time block to get connection instance from pool, after that exception is thrown.
  -	When non-positive, block till last judgement
  -</p>
  -<p>	
  -	whenExhaustedAction:
  -	0 - fail when pool is exhausted
  -	1 - block when pool is exhausted
  -	2 - grow when pool is exhausted
  -</p>
  -<p>	
  -	testOnBorrow:
  -	The pool will attempt to validate each object before it is returned from the pool
  -</p>
  -<p>	
  -	testOnReturn:
  -	The pool will attempt to validate each object before it is returned to the pool
  -</p>
  -<p>	
  -	testWhileIdle:
  -	Indicates whether or not idle objects should be validated.
  -	Objects that fail to validate will be dropped from the pool
  -</p>
  -<p>	
  -	timeBetweenEvictionRunsMillis:
  -	indicates how long the eviction thread should sleep before "runs" of examining
  -	idle objects. When non-positive, no eviction thread will be launched.
  -</p>
  -<p>	
  -	minEvictableIdleTimeMillis:
  -	specifies the minimum amount of time that a connection may sit idle
  -	in the pool before it is eligable for eviction due to idle time.
  -	When non-positive, no connection will be dropped from the pool due
  -	to idle time alone (depends on timeBetweenEvictionRunsMillis > 0)
  -</p>
  -<p>	
  -	numTestsPerEvictionRun:
  -	The number of connections to examine during each run of the
  -	idle object evictor thread (if any)
  -</p>
  -<p>	
  -	connectionFactory:
  -	The name of the connection factory implementation that is to be
  -	used. If not set, default CF is used.
  +Valid attributes for the <i>connection-pool</i> element are:
  +<ul>
  +<li>
  +maxActive<br/>
  +maximum number of connections that can be borrowed from the
  +pool at one time. When non-positive, there is no limit.
  +</li>
  +<li>
  +maxIdle<br/>
  +controls the maximum number of connections that can sit
  +idle in the pool at any time. When non-positive,
  +there is no limit
  +</li>
  +<li>
  +maxWait<br/>
  +max time block to get connection instance from pool,
  +after that exception is thrown.
  +When non-positive, block till last judgement
  +</li>
  +<li>
  +whenExhaustedAction<br/>
  +0 - fail when pool is exhausted
  +1 - block when pool is exhausted
  +2 - grow when pool is exhausted
  +</li>
  +<li>
  +testOnBorrow<br/>
  +The pool will attempt to validate each object before
  +it is returned from the pool
  +</li>
  +<li>
  +testOnReturn<br/>
  +The pool will attempt to validate each object
  +before it is returned to the pool
  +</li>
  +<li>
  +testWhileIdle<br/>
  +Indicates whether or not idle objects should be validated.
  +Objects that fail to validate will be dropped from the pool
  +</li>
  +<li>
  +timeBetweenEvictionRunsMillis<br/>
  +indicates how long the eviction thread should sleep before "runs"
  +of examining idle objects. When non-positive, no eviction
  +thread will be launched.
  +</li>
  +<li>
  +minEvictableIdleTimeMillis<br/>
  +specifies the minimum amount of time that a connection may sit idle
  +in the pool before it is eligable for eviction due to idle time.
  +When non-positive, no connection will be dropped from the pool due
  +to idle time alone (depends on timeBetweenEvictionRunsMillis > 0)
  +</li>
  +<li>
  +numTestsPerEvictionRun<br/>
  +The number of connections to examine during each run of the
  +idle object evictor thread (if any)
  +</li>
  +</ul>
   </p>
   
   <source><![CDATA[
  @@ -233,7 +241,7 @@
   	Concrete base classes, may specify a sequence of extent-class elements,
   	naming the derived classes.
   	<br/>
  -	A class-descriptor may contain user defined custom attribute elements. 
  +	A class-descriptor may contain user defined custom attribute elements.
   </p>
   <source><![CDATA[
   <!ELEMENT class-descriptor
  @@ -271,8 +279,9 @@
   <source><![CDATA[
   <!ATTLIST class-descriptor
   	class ID #REQUIRED
  -	isolation-level (read-uncommitted | read-committed | repeatable-read |
  -	                 serializable | optimistic) "read-uncommitted"
  +	isolation-level (read-uncommitted | read-committed |
  +                    repeatable-read | serializable |
  +                    optimistic) "read-uncommitted"
   	proxy CDATA #IMPLIED
   	schema CDATA #IMPLIED
   	table CDATA #IMPLIED
  @@ -641,31 +650,31 @@
   </section>
   
   <section name="the repository verifier">
  -	
  +
   author:     <a href="mailto:daren@softwarearena.com">Daren Drummond</a>
  -<br/>     
  -			
  +<br/>
  +
   version:    0.9, 07/11/2002
   <br/>
   <subsection name="introduction" >
   <p>
  -Object/Relational mapping tools can significantly decrease the time to 
  -implementation large projects because they greatly reduce the amount of 
  -custom code needed to persist data.  Unfortunately, the mapping layer that 
  -these tools use to match class fields to database fields has to be maintained 
  -during the development cycle.  All too often bugs are introduced into the 
  -system because a change to a database table or class field was not propagated 
  +Object/Relational mapping tools can significantly decrease the time to
  +implementation large projects because they greatly reduce the amount of
  +custom code needed to persist data.  Unfortunately, the mapping layer that
  +these tools use to match class fields to database fields has to be maintained
  +during the development cycle.  All too often bugs are introduced into the
  +system because a change to a database table or class field was not propagated
   all the way through the persistence chain.  Large projects undergoing lots
   of uncontrolled changes are especially susceptible to these types of bugs.
   </p>
   
   <p>
  -By using the Ant OJB VerifyMappingsTask the developer can find mapping errors 
  -in the OJB repository.xml file during the build process.  Using this Ant task 
  -will save you (the deveoloper) the trouble of starting up your EJB server, 
  +By using the Ant OJB VerifyMappingsTask the developer can find mapping errors
  +in the OJB repository.xml file during the build process.  Using this Ant task
  +will save you (the deveoloper) the trouble of starting up your EJB server,
   deploying and testing your application simply to find basic mapping errors. This
  -way, your builds can "fail fast" and help you find bugs as soon as they are 
  -introduced.  Over the lifetime of a project this will save significant 
  +way, your builds can "fail fast" and help you find bugs as soon as they are
  +introduced.  Over the lifetime of a project this will save significant
   development time and testing effort.
   </p>
   </subsection>
  @@ -673,45 +682,45 @@
   <subsection name="Using the VerifyMappingsTask">
   <ol>
     <li>
  -   Add your jdbcDriver to your ant boot classpath 
  +   Add your jdbcDriver to your ant boot classpath
      (the classpath you use to start ant)
     </li>
  -  
  -  <li> 
  +
  +  <li>
      Add the OJB jar file to your ant boot classpath
      (the classpath you use to start ant)
     </li>
  -  
  +
     <li>
      Add a taskdef tag to your build.xml file to define the VerifyMappingsTask
      (see example below)
     </li>
  -  
  -  <li> 
  +
  +  <li>
      Add the verifymappings task to an ant target (see example below).
      NOTE: Before verifymappings task runs you should have completed:<br/>
       a) Set up your database (must be running)<br/>
       b) Built all of your classes<br/>
       c) Written your repository files.<br/>
     </li>
  -  
  +
     <li>
      Optionally use the -quiet parameter when running ant to suppress warnings
      and detailed processing messages from the VerifyMappingsTask.
     </li>
  - </ol>  
  - 
  + </ol>
  +
    <p>
  - 	The VerifyMappingTask is integrated into the OJB <code>build.xml</code> 
  + 	The VerifyMappingTask is integrated into the OJB <code>build.xml</code>
    	file. You can invoke it manually by <code>build[.sh] verify</code>.
    	<br/>
  - 	On executing the junit regression tests by <code>build[.sh] junit</code>

  + 	On executing the junit regression tests by <code>build[.sh] junit</code>
    	the verify target is invoked implicitely.
    	It is invoked after compiling all code and setting up the testdatabase
    	 to verify correctness of the mapping file before running the test cases.
    </p>
  - 
  -</subsection>   
  +
  +</subsection>
   
   <subsection name="Configuration Attributes">
   <dl>
  @@ -724,41 +733,41 @@
     <dd>
     The path and file name of the to the OJB repository file. Required.
     </dd>
  -					
  -  <dt><b>verifyclasspath</b></dt>	
  +
  +  <dt><b>verifyclasspath</b></dt>
     <dd>
  -  The classpath for loading the classes specified by the 
  +  The classpath for loading the classes specified by the
     <code>&lt;class-descriptor&gt;&lt;/class-descriptor&gt;</code>
tags in the OJB repository.xml
     file.  Required.
     </dd>
   
  -  <dt><b>[ignoreFieldNameCase]</b></dt> 
  +  <dt><b>[ignoreFieldNameCase]</b></dt>
     <dd>
  -  A flag indicating if field name case will be considered when 
  +  A flag indicating if field name case will be considered when
     searching for table column names. Valid values are "true" or "false".
     Optional.
     </dd>
   
     <dt><b>[useStrictTypeChecking]</b></dt>
     <dd>
  -  A flag indicating that strict type checking of database column types will be 
  +  A flag indicating that strict type checking of database column types will be
     used when searching for column names. Valid values are "true" or "false".
  -  If this value is set to "true" then the task will log a warning if the 
  -  table column jdbc type doesn't match the type specified in the OJB 
  +  If this value is set to "true" then the task will log a warning if the
  +  table column jdbc type doesn't match the type specified in the OJB
     repository field descriptor.  Optional.
     </dd>
   
     <dt><b>[useXMLValidation]</b></dt>
     <dd>
  -  A flag indicating that W3c xml validation will be used to verify the OJB 
  +  A flag indicating that W3c xml validation will be used to verify the OJB
     repository.xml file.  Valid values are "true" or "false".  Optional.
     </dd>
   
     <dt><b>[failonerror]</b></dt>
     <dd>
  -  A flag indicating that this Ant task will throw a BuildException if it 
  -  encounters any verification errors in the repository.xml file.  In most 
  -  cases, this will have the effect of stopping the build process.  Valid 
  +  A flag indicating that this Ant task will throw a BuildException if it
  +  encounters any verification errors in the repository.xml file.  In most
  +  cases, this will have the effect of stopping the build process.  Valid
     values are "true" or "false".  Optional.
     </dd>
   
  @@ -767,37 +776,37 @@
   <p>
   Optional as a group:
   <br/>
  -If none of these attributes are specified then the task will try to use the 
  +If none of these attributes are specified then the task will try to use the
   jdbc connection information specified in the repository.xml file.  However,
   if you specify one of these attributes then you must supply all of them.
   </p>
   
   <dl>
     <dt><b>[jdbcDriver]</b></dt>
  -  <dd>        
  -       the fully qualified class name of the jdbc driver you 
  -       will use to communicate with the database. 
  +  <dd>
  +       the fully qualified class name of the jdbc driver you
  +       will use to communicate with the database.
     </dd>
  -  
  +
     <dt><b>[url]</b></dt>
     <dd>
          the connection url for your jdbc driver.  If your database
          requires you to specify a schema, then you should specify
          the schema on the url.
     </dd>
  -  
  +
     <dt><b>[logon]</b></dt>
     <dd>
          the logon account to use for the database.
     </dd>
  -  
  +
     <dt><b>[password]</b></dt>
     <dd>
  -       the password to use for the logon.	
  -  </dd>				
  +       the password to use for the logon.
  +  </dd>
   </dl>
  -					
  -</subsection>				
  +
  +</subsection>
   
   <subsection name="Example XML">
   <source><![CDATA[
  @@ -806,17 +815,17 @@
       	<path refid="compilation-classpath"/>
           <pathelement path="${build.dir}/test/ojb"/>
       </path>
  -    
  +
   <!-- Access the classpath as a property -->
  -    <property 
  -    	name="runtime.classpath" 
  +    <property
  +    	name="runtime.classpath"
       	refid="runtime-classpath"
       />
   
   <!-- Define the custom task -->
       <target name="declare" depends="main">
  -        <taskdef 
  -            name="verifymappings" 
  +        <taskdef
  +            name="verifymappings"
               classname="org.apache.ojb.broker.ant.VerifyMappingsTask"
           >
               <classpath refid="runtime-classpath" />
  @@ -824,25 +833,25 @@
       </target>
   
   <!-- set the verification options -->
  -	<target name="verify" 
  -	        depends="declare" 
  +	<target name="verify"
  +	        depends="declare"
   	        description="Verifies the ojb mapping file."
   	>
  -    	<verifymappings 
  -    		propertiesFile="${build.dir}/test/ojb/OJB.properties" 
  -        	repositoryFile="${build.dir}/test/ojb/repository.xml" 
  +    	<verifymappings
  +    		propertiesFile="${build.dir}/test/ojb/OJB.properties"
  +        	repositoryFile="${build.dir}/test/ojb/repository.xml"
           	jdbcDriver="org.hsqldb.jdbcDriver"
           	url="jdbc:hsqldb:target/test/OJB"
           	logon="sa"
  -        	password="" 
  +        	password=""
           	ignoreFieldNameCase="true"
           	useStrictTypeChecking="false"
           	verifyclasspath="${runtime.classpath}"
           	useXMLValidation="true"
           	failonerror="true"
  -        />     					
  -   	</target>  
  -	
  +        />
  +   	</target>
  +
   ]]></source>
   
   </subsection>
  
  
  

Mime
View raw message