[jboss-cvs] JBossAS SVN: r76872 - projects/docs/enterprise/4.3.3/Cache/Cache_FAQ/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: irooskov at redhat.com
Date: 2008-08-10 21:59:48 -0400 (Sun, 10 Aug 2008)
New Revision: 76872

Modified:
   projects/docs/enterprise/4.3.3/Cache/Cache_FAQ/en-US/Cache_Frequently_Asked_Questions.xml
Log:
removed occurances of 'aspectized' from the documentation


Modified: projects/docs/enterprise/4.3.3/Cache/Cache_FAQ/en-US/Cache_Frequently_Asked_Questions.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Cache/Cache_FAQ/en-US/Cache_Frequently_Asked_Questions.xml	2008-08-11 01:53:33 UTC (rev 76871)
+++ projects/docs/enterprise/4.3.3/Cache/Cache_FAQ/en-US/Cache_Frequently_Asked_Questions.xml	2008-08-11 01:59:48 UTC (rev 76872)
@@ -980,10 +980,7 @@
                <para>To solve the first kind of issue, in JBoss Cache 1.2.4 we
                   introduced the concept of a
                   <literal>TreeCacheMarshaller</literal>
-                  .
-                  Basically, this allows application code to register a classloader
-                  with a portion of the cache tree for use in handling objects
-                  replicated to that portion. See the TreeCacheMarshaller section of
+                  . This allows the code within the application to create a classloader for use with a portion of the cache tree that will handle objects replicated to that portion. See the TreeCacheMarshaller section of
                   the user guide for more details.
                </para>
 
@@ -1152,8 +1149,7 @@
                   transactional POJO (plain old Java object) cache. By POJO, we mean
                   that the cache: 1) automatically manages object mapping and
                   relationship for a client under both local and replicated cache
-                  mode, 2) provides support for inheritance relationship between
-                  "aspectized" POJOs. By leveraging the dynamic AOP in JBossAop, it is
+		  mode, 2) provides support for inheritance between POJOs created under Aspect-Oriented Programming (AOP). This allows a user to modify code at runtime without inflicting this change permanently on the program. By leveraging the dynamic AOP in JBossAop, it is
                   able to map a complex object into the cache store, preserve and
                   manage the object relationship behind the scene. During replication
                   mode, it performs fine-granularity (i.e., on a per-field basis)
@@ -1312,7 +1308,7 @@
                   option called
                   <literal>aopc</literal>
                   . You can use this option to
-                  pre-compile your "aspectized" POJO. Once the classes have been byte
+                  pre-compile your AOP created POJO. Once the classes have been byte
                   code generated, they can be treated as regular class files, i.e.,
                   you will not need to include any
                   <literal>jboss-aop.xml</literal>
@@ -1370,17 +1366,17 @@
                   <literal>Person</literal>
                   ) to be
                   "prepared", a JBossAop term to denote that the object will be
-                  "aspectized" by the system. After this declaration, JBossAop will
+                  created using AOP, by the system. After this declaration, JBossAop will
                   invoke any interceptor that associates with this POJO. PojoCache
                   will dynamically add an
                   <literal>org.jboss.cache.aop.CacheInterceptor</literal>
                   to this POJO
                   to perform object mapping and relationship management.
                </para>
-
-               <para>Note that to add your POJO, you should declare all the fields
-                  to be "prepared" as in the example.
+		<note>
+               <para>To add your POJO, you should declare all the fields to be "prepared" as in the example.
                </para>
+       		</note>
             </answer>
          </qandaentry>
 
@@ -1505,7 +1501,7 @@
 
          <qandaentry>
             <question>
-               <para>When I declare my POJO to be "aspectized", what happens to the
+               <para>When I declare my POJO to be created using AOP, what happens to the
                   fields with transient, static, and final modifiers?
                </para>
             </question>
@@ -1588,7 +1584,7 @@
                   <literal>Set</literal>
                   , and
                   <literal>Map</literal>
-                  without users to declare them "aspectized".
+                  without users to declare them as being created using Aspect-Oriented Programming.
                   It is done via a dynamic proxy. Here is a code snippet to use an
                   <literal>ArrayList</literal>
                   proxy class.
@@ -1668,7 +1664,7 @@
 
          <qandaentry>
             <question>
-               <para>What happens when my "aspectized" POJO has field members that
+               <para>What happens when my AOP POJO has field members that
                   are of Collection class ?
                </para>
             </question>