[jboss-cvs] JBossCache/examples/PojoCache ...

[Ben Wang]

  User: bwang   
  Date: 06/09/25 04:02:31

  Modified:    examples/PojoCache  readme.txt
  Log:
  upd
  
  Revision  Changes    Path
  1.4       +38 -40    JBossCache/examples/PojoCache/readme.txt
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: readme.txt
  ===================================================================
  RCS file: /cvsroot/jboss/JBossCache/examples/PojoCache/readme.txt,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -b -r1.3 -r1.4
  --- readme.txt	5 Feb 2006 11:57:07 -0000	1.3
  +++ readme.txt	25 Sep 2006 08:02:31 -0000	1.4
  @@ -1,41 +1,39 @@
  -In this folder can be found a number of examples illustrating how to use
  -JBossCacheAop (POJO Cache).  Two different sample applications are provided, and
  -different mechanisms for instrumenting the classes in the applications' domain
  -model are shown.
  -
  -In the "sensor" subdirectory, an application that uses JBossCacheAop to model
  -the state of sensor network on a high speed rail line is shown.  This example
  -uses JDK 1.4 style annotations, with annoc and aopc used to instrument
  -the classes before deployment.  The example will be further examined in a
  -forthcoming issue of OnJava.
  -
  -The "sensor" example also allows a user to use beanshell to manipulate the
  -objects in the cache.
  -
  -In the "annotated50", "annotated14", "non-annotated" and "loadtime" subdirectories,
  -the example application illustrates using JBossCacheAop (PojoCache) to replicate
  -over a cluster state information about students and the courses they take.  The
  -different versions of the example illustrate different mechanisms for
  -instrumenting the domain model classes for use in JBossCacheAop.
  -
  -In the "annotated50" example, JDK50 annotation are used (therefore JDK50 is required).
  -You can either run it directly (through loadtime mode) or using aopc first (compile
  -time mode). Of course, the annotation has to be attached to the POJOs first. Then,
  -there is another system-wide "jboss-aop.xml" that is needed but is read-only.
  -
  -In the "annotated14" example, JDK 1.4 style annotation are used, with
  -annoc and aopc used to pre-compile the classes.  Because annotations are
  -used, a standardized jboss-aop.xml can be used to drive aopc.
  -
  -In the "non-annotated" example, no annotations are used, although aopc
  -pre-compilation is still used.  In this example, the jboss-aop.xml file used
  -to drive aopc needs to specifically describe how to instrument the classes in
  -the domain model.
  -
  -In the "loadtime" example, no pre-compilation is performed -- the domain model
  -classes are instrumented at load time. Again, in this example, the jboss-aop.xml
  -file used to drive aopc needs to specifically describe how to instrument the
  -classes in the domain model.
  +In this folder can be found a number of examples illustrating 
  +how to use PojoCache. Two different sample applications are 
  +provided, and different mechanisms for instrumenting the 
  +classes in the applications' domain model are shown.
  +
  +In the "sensor" subdirectory, an application that uses PojoCache 
  +to model the state of sensor network on a high speed rail line 
  +is shown.  This example uses JDK5.0 style annotations, with aopc 
  +used to instrument the classes before deployment. The example 
  +has been published in OnJava.
  +
  +The "sensor" example also allows a user to use beanshell to 
  +manipulate the objects in the cache.
  +
  +In the "annotated50", "non-annotated" and "loadtime" subdirectories,
  +the example application illustrates using PojoCache to replicate
  +over a cluster state information about students and the courses 
  +they take. The different versions of the example illustrate 
  +different mechanisms for instrumenting the domain model classes 
  +for use in PojoCache.
  +
  +In the "annotated50" example, JDK50 annotation are used. You can 
  +either run it directly (through loadtime mode) or using aopc first 
  +(compile time mode). Of course, the annotation has to be attached 
  +to the POJOs first. Then, there is another system-wide 
  +"pojocache-aop.xml" that is needed but is mostly read-only.
  +
  +In the "non-annotated" example, no annotations are used, although 
  +aopc pre-compilation is still used.  In this example, the 
  +user-aop.xml file used to drive aopc needs to specifically describe 
  +how to instrument the classes in the domain model.
  +
  +In the "loadtime" example, no pre-compilation is performed -- the 
  +domain model classes are instrumented at load time. Again, in this 
  +example, the pojocache-aop.xml file used to drive aopc needs to 
  +specifically describe how to instrument the classes in the domain model.
   
  -See the "readme.txt" file in each subdirectory for more on how to use that
  -particular example.
  +See the "readme.txt" file in each subdirectory for more on how to 
  +use that particular example.