[jboss-cvs] JBossAS SVN: r76874 - in projects/docs/enterprise/4.2.5/Cache: Cache_Pojo_Cache_Guide/en-US and 2 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Aug 10 22:32:29 EDT 2008
Author: irooskov at redhat.com
Date: 2008-08-10 22:32:29 -0400 (Sun, 10 Aug 2008)
New Revision: 76874
Modified:
projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Author_Group.xml
projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Cache_Frequently_Asked_Questions.xml
projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Architecture.xml
projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Author_Group.xml
projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Instrumentation.xml
projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Introduction.xml
projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Term.xml
projects/docs/enterprise/4.2.5/Cache/Cache_Tree_Cache_Guide/en-US/Author_Group.xml
projects/docs/enterprise/4.2.5/Cache/Cache_Tree_Cache_Guide/en-US/Book_Info.xml
projects/docs/enterprise/4.2.5/Cache/Cache_Tutorial/en-US/Author_Group.xml
projects/docs/enterprise/4.2.5/Cache/Cache_Tutorial/en-US/Book_Info.xml
Log:
updated Cache 4.2.5 documentation so that the word 'aspectized' is not present
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Author_Group.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Author_Group.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -1,40 +1,10 @@
<?xml version='1.0'?>
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<authorgroup id="AuthorGroup">
- <author>
- <firstname>Ben</firstname>
- <surname>Wang</surname>
-
- <email>ben.wang at jboss.com</email>
- </author>
-
- <author>
- <firstname>Bela</firstname>
- <surname>Ban</surname>
-
- <email>bela at jboss.com</email>
- </author>
-
- <author>
- <firstname>Manik</firstname>
- <surname>Surtani</surname>
-
- <email>manik at jboss.org</email>
- </author>
-
- <author>
- <firstname>Scott</firstname>
- <surname>Marlow</surname>
- <email>smarlow at novell.com</email>
- </author>
-
- <author>
- <firstname>Galder</firstname>
- <surname>Zamarreño</surname>
- <email>galder.zamarreno at jboss.com</email>
- </author>
-
+<authorgroup>
+ <author><firstname>Ben Wang, Bela Ban, Manik Surtani, Scott Marlow, Galder Zamarreño </firstname></author>
+
</authorgroup>
+
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Book_Info.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Book_Info.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -6,9 +6,9 @@
]>
<bookinfo>
- <title>JBoss Cache</title>
+ <title>JBoss Cache 1.4.1</title>
<subtitle>Frequently Asked Questions</subtitle>
- <issuenum>1.4.1</issuenum>
+ <issuenum>4.3</issuenum>
<productnumber>0</productnumber>
<pubdate>June, 2007</pubdate>
<abstract>
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Cache_Frequently_Asked_Questions.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Cache_Frequently_Asked_Questions.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_FAQ/en-US/Cache_Frequently_Asked_Questions.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -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>
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Architecture.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Architecture.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -13,7 +13,7 @@
</para>
<sect1 id="Architecture-Dynamic_AOP_interception"><title>Dynamic AOP interception</title>
<para>
- JBossAop provides an API (<literal>appendInterceptor</literal>) to add an interceptor at runtime. PojoCache uses this feature extensively to provide user transparency. Every "aspectized" POJO class will have an associated <literal>org.jboss.aop.InstanceAdvisor</literal> instance. During a <literal>putObject(FQN fqn, Object pojo)</literal> operation (API explained below), PojoCache will examine to see if there is already a <literal>org.jboss.cache.aop.CacheInterceptor</literal> attached. (Note that a <literal>CacheInterceptor</literal> is the entrance of PojoCache to dynamically manage cache contents.) If it has not, one will be added to <literal>InstanceAdvisor</literal> object. Afterward, any POJO field modification will invoke the corresponding <literal>CacheInterceptor</literal> instance. Below is a schematic illustration of this process.
+ JBossAop provides an API (<literal>appendInterceptor</literal>) to add an interceptor at runtime. PojoCache uses this feature extensively to provide user transparency. Every Aspect-Oreinted Programming (AOP) created POJO class will have an associated <literal>org.jboss.aop.InstanceAdvisor</literal> instance. During a <literal>putObject(FQN fqn, Object pojo)</literal> operation (API explained below), PojoCache will examine to see if there is already a <literal>org.jboss.cache.aop.CacheInterceptor</literal> attached. (Note that a <literal>CacheInterceptor</literal> is the entrance of PojoCache to dynamically manage cache contents.) If it has not, one will be added to <literal>InstanceAdvisor</literal> object. Afterward, any POJO field modification will invoke the corresponding <literal>CacheInterceptor</literal> instance. Below is a schematic illustration of this process.
</para>
<para>
JBossAop has the capability to intercept both method level call and field level read write. From the perspective of PojoCache, field level interception is the appropriate mechanism to synchronize with the backend cache store. Please note that, <itemizedlist>
@@ -134,12 +134,12 @@
tree.startService(); // kick start tree cache
tree.putObject("/aop/joe", joe); // add aop sanctioned object (and sub-objects) into cache.
-// since it is aspectized, use of plain get/set methods will take care
+// since it is created using AOP, use of plain get/set methods will take care
// of cache contents automatically.
joe.setAge(41);
</programlisting>
<para>
- Note that a typical <literal>PojoCache</literal> usage involves instantiating the <literal>PojoCache</literal> , configuring, and starting the cache instance. Then, a user creates the aspectized POJO that will be put into the cache using <literal>putObject()</literal> API.
+ Note that a typical <literal>PojoCache</literal> usage involves instantiating the <literal>PojoCache</literal> , configuring, and starting the cache instance. Then, a user creates the AOP POJO that will be put into the cache using <literal>putObject()</literal> API.
</para>
<para>
In addition, PojoCache also supports get/set with parameter type of some <literal>Collection</literal> classes (i.e., <literal>List</literal> , <literal>Map</literal> , and <literal>Set</literal> ) automatically. For example, the following code snippet in addition to the above example will trigger PojoCache to manage the states for the <literal>Languages</literal> list as well. The following figure illustrates the node structure from the replicated GUI point of view. Details of Collection class support will be given later.
@@ -270,7 +270,7 @@
</programlisting>
</sect1><sect1 id="Architecture-Collection_class_proxy"><title>Collection class proxy</title>
<para>
- The POJO classes that inherit from <literal>Set</literal> , <literal>List</literal> , and <literal>Map</literal> are treated as "aspectized" automatically. That is, users need not declare them "prepared" in the xml configuration file or via annotation. Since we are not allowed to instrument the Java system library, we will use a proxy approach instead. That is, when we encounter any Collection instance, we will: <itemizedlist>
+ The POJO classes that inherit from <literal>Set</literal> , <literal>List</literal> , and <literal>Map</literal> are treated as AOP created automatically. That is, users need not declare them "prepared" in the xml configuration file or via annotation. Since we are not allowed to instrument the Java system library, we will use a proxy approach instead. That is, when we encounter any Collection instance, we will: <itemizedlist>
<listitem>
<para>Create a Collection proxy instance and place it in the cache (instead of the original reference). The mapping of the Collection elements will still be carried out recursively as expected.</para>
</listitem>
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Author_Group.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Author_Group.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -1,19 +1,8 @@
<?xml version='1.0'?>
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<authorgroup id="AuthorGroup">
- <author>
- <firstname>Ben</firstname>
- <surname>Wang</surname>
-
- <email>ben.wang at jboss.com</email>
- </author>
-
- <author>
- <firstname>Scott</firstname>
- <surname>Marlow</surname>
-
- <email>smarlow at novell.com</email>
- </author>
-
-</authorgroup>
+
+<authorgroup>
+ <author><firstname>Ben Wang, Scott Marlow</firstname></author>
+
+</authorgroup>
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Book_Info.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Book_Info.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -7,9 +7,9 @@
]>
<bookinfo id="Pojo_Cache">
- <title>Pojo Cache</title>
+ <title>Pojo Cache 1.4.1</title>
<subtitle>User Guide</subtitle>
- <issuenum>1.4.1 "Cayenne"</issuenum>
+ <issuenum>4.3</issuenum>
<productnumber>0</productnumber>
<abstract>
<para>
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Instrumentation.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Instrumentation.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Instrumentation.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -34,7 +34,7 @@
</aop>
</programlisting>
<para>
- Detailed semantics of <literal>jboss-aop.xml</literal> can again be found in JBossAop. But above statements basically declare all field read and write operations in classes <code>Address</code> and <code>Person</code> will be "prepared" (or "aspectized"). Note that:
+ Detailed semantics of <literal>jboss-aop.xml</literal> can again be found in JBossAop. But above statements basically declare all field read and write operations in classes <code>Address</code> and <code>Person</code> will be "prepared" (or created using AOP). Note that:
</para>
<itemizedlist>
<listitem>
@@ -44,7 +44,7 @@
<para>You can potentially replace specific class name with wildcard that includes all the POJOs inside the same package space</para>
</listitem>
<listitem>
- <para>The <code>instanceof</code> operator declares any sub-type or sub-class of the specific POJO will also be "aspectized". For example, if a <code>Student</code> class is a subclass of <code>Person</code> , JBossAop will automatically instrument it as well!</para>
+ <para>The <code>instanceof</code> operator declares any sub-type or sub-class of the specific POJO will also be created using AOP. For example, if a <code>Student</code> class is a subclass of <code>Person</code> , JBossAop will automatically instrument it as well!</para>
</listitem>
<listitem>
<para>We intercept the field of all access levels (i.e., <literal>private</literal> , <literal>protected</literal> , <literal>public</literal> , etc.) The main reason being that we consider all fields as stateful data. However, we can relax this requirement in the future if there is a use case for it.</para>
@@ -72,7 +72,7 @@
<prepare expr="field(* $instanceof{@@org.jboss.cache.aop.InstanceOfAopMarker}->*)" />
</aop>
</programlisting>
- Basically, it simply states that any annotation with both marker interfaces will be "aspectized" accordingly.
+ Basically, it simply states that any annotation with both marker interfaces will be coded using AOP accordingly.
</para>
<para>
Here is two code snippets that illustrate the declaration of both types through 1.4 style annotation:
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Introduction.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Introduction.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Introduction.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -108,12 +108,12 @@
</listitem>
<listitem>
<para>
- Inheritance relationship. PojoCache preserves the POJO inheritance hierarchy after the object item is stored in the cache. For example, if a <literal>Student</literal> class inherits from a <keycode>Person</keycode> class, once a <literal>Student</literal> object is mapped to PojoCache (e.g., <literal>putObject</literal> call), the attributes in base class <literal>Person</literal> is "aspectized" as well.
+ Inheritance relationship. PojoCache preserves the POJO inheritance hierarchy after the object item is stored in the cache. For example, if a <literal>Student</literal> class inherits from a <keycode>Person</keycode> class, once a <literal>Student</literal> object is mapped to PojoCache (e.g., <literal>putObject</literal> call), the attributes in base class <literal>Person</literal> is coded using Aspect-Oriented Programming (AOP) as well.
</para>
</listitem>
<listitem>
<para>
- Support Collection classes (e.g., List, Set, and Map based objects) automatically without declaring them as aop-enabled. That is, you can use them either as a plain POJO or a sub-object to POJO without declaring them as "aspectized". In addition, it supports runtime swapping of the proxy reference as well.
+ Support Collection classes (e.g., List, Set, and Map based objects) automatically without declaring them as aop-enabled. That is, you can use them either as a plain POJO or a sub-object to POJO without declaring them as coded using AOP. In addition, it supports runtime swapping of the proxy reference as well.
</para>
</listitem>
<listitem>
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Term.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Term.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_Pojo_Cache_Guide/en-US/Term.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -74,7 +74,7 @@
<term>Prepare</term>
<listitem>
<para>
- Prepare is a keyword in JBossAop pointcut language used to specify which POJO needs to be instrumented. It appears in a <literal>jboss-aop.xml</literal> file. However, if you can use annotation to specify the POJO instrumentation, there is no need for a <literal>jboss-aop.xml</literal> listing. Note that When a POJO is declared properly either through the xml or annotation, we consider it "aspectized".
+ Prepare is a keyword in JBossAop pointcut language used to specify which POJO needs to be instrumented. It appears in a <literal>jboss-aop.xml</literal> file. However, if you can use annotation to specify the POJO instrumentation, there is no need for a <literal>jboss-aop.xml</literal> listing.
</para>
</listitem>
</varlistentry>
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_Tree_Cache_Guide/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_Tree_Cache_Guide/en-US/Author_Group.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_Tree_Cache_Guide/en-US/Author_Group.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -1,37 +1,8 @@
<?xml version='1.0'?>
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<authorgroup id="AuthorGroup">
- <author>
- <firstname>Ben</firstname>
- <surname>Wang</surname>
-
- <email>ben.wang at jboss.com</email>
- </author>
+
+<authorgroup>
+ <author><firstname>Ben Wang, Bela Ban, Manik Surtani, Brian Stansberry, Daniel Huang</firstname></author>
- <author>
- <firstname>Bela</firstname>
- <surname>Ban</surname>
-
- <email>bela at jboss.com</email>
- </author>
- <author>
- <firstname>Manik</firstname>
- <surname>Surtani</surname>
-
- <email>manik at jboss.org</email>
- </author>
- <author>
- <firstname>Brian</firstname>
- <surname>Stansberry</surname>
-
- <email>brian.stansberry at jboss.com</email>
- </author>
- <author>
- <firstname>Daniel</firstname>
- <surname>Huang</surname>
-
- <email>dhuang at jboss.org</email>
- </author>
-
-</authorgroup>
+</authorgroup>
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_Tree_Cache_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_Tree_Cache_Guide/en-US/Book_Info.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_Tree_Cache_Guide/en-US/Book_Info.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -7,9 +7,9 @@
]>
<bookinfo id="JBoss_Cache_Tree_Cache___A_Structured_Replicated_Transactional_Cache">
- <title>JBoss Cache Tree Cache</title>
+ <title>JBoss Cache Tree Cache 1.4.1</title>
<subtitle>A Structured, Replicated, Transactional Cache</subtitle>
- <issuenum>1.4.1 "Cayenne"</issuenum>
+ <issuenum>4.3</issuenum>
<productnumber>0</productnumber>
<abstract>
<para>
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_Tutorial/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_Tutorial/en-US/Author_Group.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_Tutorial/en-US/Author_Group.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -1,19 +1,8 @@
<?xml version='1.0'?>
<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<authorgroup id="AuthorGroup">
- <author>
- <firstname>Ben</firstname>
- <surname>Wang</surname>
-
- <email>ben.wang at jboss.com</email>
- </author>
+
+<authorgroup>
+ <author><firstname>Ben Wang, Bela Ban</firstname></author>
- <author>
- <firstname>Bela</firstname>
- <surname>Ban</surname>
-
- <email>bela at jboss.com</email>
- </author>
-
-</authorgroup>
+</authorgroup>
Modified: projects/docs/enterprise/4.2.5/Cache/Cache_Tutorial/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Cache/Cache_Tutorial/en-US/Book_Info.xml 2008-08-11 02:15:59 UTC (rev 76873)
+++ projects/docs/enterprise/4.2.5/Cache/Cache_Tutorial/en-US/Book_Info.xml 2008-08-11 02:32:29 UTC (rev 76874)
@@ -9,7 +9,7 @@
<bookinfo id="JBoss_Cache">
<title>JBoss Cache</title>
<subtitle>TreeCache and PojoCache Tutorial</subtitle>
- <issuenum>4.2.0</issuenum>
+ <issuenum>4.3</issuenum>
<productnumber>1</productnumber>
<abstract>
<para>
More information about the jboss-cvs-commits
mailing list