db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bri...@apache.org
Subject cvs commit: db-ojb/xdocs repository.xml
Date Sun, 04 Jan 2004 04:34:15 GMT
brianm      2004/01/03 20:34:15

  Modified:    src/test/org/apache/ojb build.xml
               xdocs    repository.xml
  Log:
  Proxy prefetching description added (description is still weak, but wanted to get it in
before 1.0)
  
  Revision  Changes    Path
  1.2       +11 -0     db-ojb/src/test/org/apache/ojb/build.xml
  
  Index: build.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/test/org/apache/ojb/build.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- build.xml	18 Sep 2003 02:32:17 -0000	1.1
  +++ build.xml	4 Jan 2004 04:34:15 -0000	1.2
  @@ -59,6 +59,17 @@
           <delete file="velocity.log"/>
       </target>
   
  +    <target name="repository-files">
  +        <taskdef name="ojbdoclet"
  +            classname="xdoclet.modules.ojb.OjbDocletTask"
  +            classpathref="compile-classpath" />
  +            <ojbdoclet destdir="./build">
  +                <fileset dir="./src/java"/>
  +                <ojbrepository destinationFile="repository_user.xml"/>
  +                <torqueschema databaseName="kendra" destinationFile="kendra_schema.xml"/>
  +            </ojbdoclet>
  +    </target>
  +
       <target name="jar" depends="build">
           <mkdir dir="${target.dir}"/>
           <jar index="true" jarfile="${target.dir}/${jar.name}">
  
  
  
  1.23      +24 -0     db-ojb/xdocs/repository.xml
  
  Index: repository.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/xdocs/repository.xml,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- repository.xml	15 Dec 2003 10:19:32 -0000	1.22
  +++ repository.xml	4 Jan 2004 04:34:15 -0000	1.23
  @@ -115,6 +115,11 @@
   	shipped with that relase.
   	This strictness maybe inconvenient but it does help to avoid the
   	most common version conflicts.
  +<br /><br />
  +The proxy-prefetching-limit attribute specifies a default value to be
  +applied to all proxy instances. If none is specified a default value of
  +50 is used. Proxy prefetching specifies how many instances of a proxied
  +class should be loaded in a single query when the proxy is first accessed.
   </p>
   <source><![CDATA[
   <!ATTLIST descriptor-repository
  @@ -122,6 +127,7 @@
   	isolation-level (read-uncommitted | read-committed |
                       repeatable-read | serializable |
                       optimistic) "read-uncommitted"
  +    proxy-prefetching-limit CDATA "50"
   >
   ]]></source>
   
  @@ -461,6 +467,11 @@
       proxies are used. If set to another value this value is interpreted
       as the full-qualified name of the proxy class to use.
   <br/><br/>
  +    The proxy-prefetch-limit attribute specifies a limit to the number of
  +    elements loaded on a proxied reference. When the first proxied
  +    element is loaded, a number up to the proxy-prefetch-limit will
  +    be loaded in addition.
  +<br /><br />
   	The schema attribute may contain the database schema owning the table
   	mapped to this class.
   <br/><br/>
  @@ -493,6 +504,7 @@
   	isolation-level (read-uncommitted | read-committed |
           repeatable-read | serializable | optimistic) "read-uncommitted"
   	proxy CDATA #IMPLIED
  +	proxy-prefetching-limit CDATA #IMPLIED
   	schema CDATA #IMPLIED
   	table CDATA #IMPLIED
   	row-reader CDATA #IMPLIED
  @@ -669,6 +681,11 @@
   	The proxy attribute can be set to true to specify that proxy based
   	lazy loading should be used for this attribute.
   <br/><br/>
  +    The proxy-prefetch-limit attribute specifies a limit to the number of
  +    elements loaded on a proxied reference. When the first proxied
  +    element is loaded, a number up to the proxy-prefetch-limit will
  +    be loaded in addition.
  +<br /><br />
   	The refresh attribute can be set to true to force OJB to refresh
   	object references on instance loading.
   <br/><br/>
  @@ -691,6 +708,7 @@
   	class-ref IDREF #REQUIRED
   
   	proxy (true | false) "false"
  +	proxy-prefetching-limit CDATA #IMPLIED
   	refresh (true | false) "false"
   
   	auto-retrieve (true | false) "true"
  @@ -777,6 +795,11 @@
   	The proxy attribute can be set to true to specify that proxy based
   	lazy loading should be used for this attribute.
   <br/><br/>
  +    The proxy-prefetch-limit attribute specifies a limit to the number of
  +    elements loaded on a proxied reference. When the first proxied
  +    element is loaded, a number up to the proxy-prefetch-limit will
  +    be loaded in addition.
  +<br /><br />
   	The refresh attribute can be set to true to force OJB to refresh
   	object and collection references on instance loading.
   <br/><br/>
  @@ -804,6 +827,7 @@
   	indirection-table CDATA #IMPLIED
   
   	proxy (true | false) "false"
  +	proxy-prefetching-limit CDATA #IMPLIED
   	refresh (true | false) "false"
   
   	auto-retrieve (true | false) "true"
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message