db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From t...@apache.org
Subject cvs commit: db-ojb/xdocs tutorial3.xml
Date Tue, 17 Jun 2003 20:49:16 GMT
thma        2003/06/17 13:49:16

  Modified:    xdocs    tutorial3.xml
  provide a clear statement that dynamic proxies are sufficient for almost all scenarios
  Revision  Changes    Path
  1.23      +21 -1     db-ojb/xdocs/tutorial3.xml
  Index: tutorial3.xml
  RCS file: /home/cvs/db-ojb/xdocs/tutorial3.xml,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- tutorial3.xml	14 Jun 2003 12:46:23 -0000	1.22
  +++ tutorial3.xml	17 Jun 2003 20:49:15 -0000	1.23
  @@ -790,7 +790,27 @@
   Proxy classes can be used for &quot;lazy loading&quot; aka &quot;lazy
   materialization&quot;. Using Proxy classes can help you in reducing
  -unneccessary db lookups. As an example we take a ProductGroup object
  +unneccessary db lookups. 
  +There are two kind of proxy mechanisms available:
  +	<li>
  +		Dynamic proxies provided by OJB. 
  +		They can simply be activated by setting certain switches in repository.xml.
  +		This is the solution recommemded for <b>most</b> cases.
  +		If your are in doubt use dynamic proxies.
  +	</li>
  +	<li>
  +		User defined proxies. They require the user to write
  +		proxy implementations
  +	</li>
  +As it is important to understand the mechanics of the proxy mechanism
  +I highly recommend to read this section before turning to the next sections
  +"using dynamic proxies", "using a single proxy for a whole collection" and 
  +"using a proxy for a reference", covering dynamic proxies.
  +As a simple example we take a ProductGroup object
   <code>pg</code> which contains a collection
   of 15 Article objects. Now we examine what happens when pg is loaded
   from the database:

View raw message