JBoss Cache SVN: r8317 - enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US.
by jbosscache-commits＠lists.jboss.org
Author: laubai
Date: 2009-12-09 23:47:53 -0500 (Wed, 09 Dec 2009)
New Revision: 8317
Modified:
enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/basic_api.xml
enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/configuration.xml
enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/deployment.xml
Log:
Added first part of changes for JBPAPP-2964.
Modified: enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/basic_api.xml
===================================================================
--- enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/basic_api.xml 2009-12-10 04:47:19 UTC (rev 8316)
+++ enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/basic_api.xml 2009-12-10 04:47:53 UTC (rev 8317)
@@ -21,7 +21,7 @@
</para>
<para>
- Note that the diagram above only depicts some of the more popular API methods. Reviewing the javadoc for the
+ Note that the diagram above only depicts some of the more popular API methods. Reviewing the Javadoc for the
above interfaces is the best way to learn the API. Below, we cover some of the main points.
</para>
</section>
@@ -190,7 +190,7 @@
</para>
<para>
- The <literal>Fqn</literal> class provides are variety of factory methods; see the javadoc for all the
+ The <literal>Fqn</literal> class provides are variety of factory methods; see the Javadoc for all the
possibilities. The following illustrates the most commonly used approaches to creating an Fqn:
</para>
@@ -307,7 +307,7 @@
cache.addCacheListener(myListener);
]]></programlisting>
<para>
- Similar methods exist for removing or querying registered listeners. See the javadocs on the
+ Similar methods exist for removing or querying registered listeners. See the Javadocs on the
<literal>Cache</literal> interface for more details.
</para>
<para>
@@ -511,7 +511,7 @@
</itemizedlist>
</para>
<para>
- Refer to the javadocs on the annotations as well as the
+ Refer to the Javadocs on the annotations as well as the
<literal>Event</literal> subtypes for details of what is passed in to your method, and when.
</para>
<para>
@@ -553,7 +553,7 @@
<para>
By default, all notifications are synchronous, in that they happen on the thread of the caller which generated
the event. As such, it is good practise to ensure cache listener implementations don't hold up the thread in
- long-running tasks. Alternatively, you could set the <literal>CacheListener.sync()</literal> attribute to
+ long-running tasks. Alternatively, you could set the <literal>CacheListener.sync</literal> attribute to
<literal>false</literal>, in which case you will not be notified in the caller's thread. See the
<xref linkend="element.listeners" /> on tuning this thread pool and size of blocking
queue.
Modified: enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/configuration.xml
===================================================================
--- enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/configuration.xml 2009-12-10 04:47:19 UTC (rev 8316)
+++ enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/configuration.xml 2009-12-10 04:47:53 UTC (rev 8317)
@@ -102,14 +102,16 @@
</para>
<programlisting role="JAVA"><![CDATA[
- Configuration config = new Configuration();
- config.setTransactionManagerLookupClass( GenericTransactionManagerLookup.class.getName() );
- config.setIsolationLevel(IsolationLevel.READ_COMMITTED);
- config.setCacheMode(CacheMode.LOCAL);
- config.setLockAcquisitionTimeout(15000);
+Configuration config = new Configuration();
+config.setTransactionManagerLookupClass(
+ GenericTransactionManagerLookup.class.getName()
+ );
+config.setIsolationLevel(IsolationLevel.READ_COMMITTED);
+config.setCacheMode(CacheMode.LOCAL);
+config.setLockAcquisitionTimeout(15000);
- CacheFactory factory = new DefaultCacheFactory();
- Cache cache = factory.createCache(config);
+CacheFactory factory = new DefaultCacheFactory();
+Cache cache = factory.createCache(config);
]]></programlisting>
<para>
@@ -143,8 +145,8 @@
<literal>Configuration</literal>
class and its
<xref linkend="configuration.elements" />
- are all Java Beans that expose all config elements via simple setters
- and getters. Therefore, any good IOC framework such as Spring, Google Guice, JBoss Microcontainer, etc. should be able to
+ are all Java Beans that expose all configuration elements via simple setters
+ and getters. Therefore, any good IOC framework such as JBoss Microcontainer should be able to
build up a
<literal>Configuration</literal>
from an XML file in
@@ -177,7 +179,7 @@
<para>
Following is a brief overview of the components of a
<literal>Configuration</literal>
- . See the javadoc and the linked
+ . See the Javadoc and the linked
chapters in this book for a more complete explanation of the
configurations associated with each component.
@@ -299,7 +301,7 @@
<section id="configuration.options">
<title>Overriding the Configuration via the Option API</title>
<para>
- The Option API allows you to override certain behaviours of the cache on a per invocation basis.
+ The Option API allows you to override certain behaviors of the cache on a per invocation basis.
This involves creating an instance of
<literal>org.jboss.cache.config.Option</literal>
, setting the options
@@ -330,7 +332,7 @@
node.put("localCounter", new Integer(2));
]]></programlisting>
<para>
- See the javadocs on the
+ See the Javadocs on the
<literal>Option</literal>
class for details on the options available.
</para>
Modified: enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/deployment.xml
===================================================================
--- enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/deployment.xml 2009-12-10 04:47:19 UTC (rev 8316)
+++ enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/deployment.xml 2009-12-10 04:47:53 UTC (rev 8317)
@@ -28,7 +28,7 @@
<para>
After creation, you could share your cache instance among different application components either by using an
- IOC container such as Spring, JBoss Microcontainer, etc., or by binding it to JNDI, or simply
+ IOC container such as JBoss Microcontainer, or by binding it to JNDI, or simply
holding a static reference to the cache.
</para>
@@ -140,7 +140,7 @@
]]></programlisting>
<para>
- See <ulink url="http://www.jboss.org/jbossmc/docs">the JBoss Microcontainer documentation</ulink>
+ See <ulink url="http://www.jboss.org/jbossmc">the JBoss Microcontainer documentation</ulink>
for details on the above syntax. Basically, each
<literal>bean</literal>
element represents an object and is used to create a
@@ -198,7 +198,7 @@
cache has already been started.</para>
</listitem>
</itemizedlist>
- See the <literal>CacheJmxWrapperMBean</literal> javadoc for more details.
+ See the <literal>CacheJmxWrapperMBean</literal> Javadoc for more details.
</para>
<para>
If a <literal>CacheJmxWrapper</literal> is registered, JBoss Cache also provides MBeans
@@ -219,11 +219,8 @@
deploying your cache.
</para>
- <section id="jmx.registration.programatic">
- <title>Programatic Registration</title>
-
<section id="jmx.registration.programatic.construct">
- <title>With a Cache instance</title>
+ <title>Programatic Registration with a Cache instance</title>
<para>
Simplest way to do this is to create your <literal>Cache</literal> and pass it to the
<literal>JmxRegistrationManager</literal> constructor.
@@ -252,7 +249,7 @@
</section>
<section id="jmx.registration.programatic.cfg">
- <title>With a Configuration instance</title>
+ <title>Programatic Registration with a Configuration instance</title>
<para>
Alternatively, build a <literal>Configuration</literal> object and pass it to the
<literal>CacheJmxWrapper</literal>. The wrapper will construct the <literal>Cache</literal> on your
@@ -282,7 +279,6 @@
wrapper.destroy();
]]></programlisting>
</section>
- </section>
<section>
<title>JMX-Based Deployment in JBoss AS (JBoss AS 5.x)</title>
@@ -395,7 +391,7 @@
<para>
If a <literal>CacheJmxWrapper</literal> is registered with JMX, the wrapper also ensures that
an MBean is registered in JMX for each interceptor and component that exposes statistics.
- <footnote>
+ <note>
<para>
Note that if the
<literal>CacheJmxWrapper</literal>
@@ -408,7 +404,7 @@
that this sort of "discovery" of the JMX environment was beyond the proper scope of
a caching library, so we removed this functionality.
</para>
- </footnote>.
+ </note>.
Management tools can then access those MBeans to examine the statistics. See the section in the
<xref linkend="jmx_reference.statistics" />
pertaining to the statistics that are made available via JMX.
14 years, 5 months
- 1
- 0
JBoss Cache SVN: r8316 - enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US.
by jbosscache-commits＠lists.jboss.org
Author: laubai
Date: 2009-12-09 23:47:19 -0500 (Wed, 09 Dec 2009)
New Revision: 8316
Modified:
enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/basic_api.xml
enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/configuration.xml
enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/deployment.xml
Log:
Added first part of changes for JBPAPP-2964.
Modified: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/basic_api.xml
===================================================================
--- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/basic_api.xml 2009-12-09 07:23:06 UTC (rev 8315)
+++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/basic_api.xml 2009-12-10 04:47:19 UTC (rev 8316)
@@ -21,7 +21,7 @@
</para>
<para>
- Note that the diagram above only depicts some of the more popular API methods. Reviewing the javadoc for the
+ Note that the diagram above only depicts some of the more popular API methods. Reviewing the Javadoc for the
above interfaces is the best way to learn the API. Below, we cover some of the main points.
</para>
</section>
@@ -190,7 +190,7 @@
</para>
<para>
- The <literal>Fqn</literal> class provides are variety of factory methods; see the javadoc for all the
+ The <literal>Fqn</literal> class provides are variety of factory methods; see the Javadoc for all the
possibilities. The following illustrates the most commonly used approaches to creating an Fqn:
</para>
@@ -307,7 +307,7 @@
cache.addCacheListener(myListener);
]]></programlisting>
<para>
- Similar methods exist for removing or querying registered listeners. See the javadocs on the
+ Similar methods exist for removing or querying registered listeners. See the Javadocs on the
<literal>Cache</literal> interface for more details.
</para>
<para>
@@ -511,7 +511,7 @@
</itemizedlist>
</para>
<para>
- Refer to the javadocs on the annotations as well as the
+ Refer to the Javadocs on the annotations as well as the
<literal>Event</literal> subtypes for details of what is passed in to your method, and when.
</para>
<para>
@@ -553,7 +553,7 @@
<para>
By default, all notifications are synchronous, in that they happen on the thread of the caller which generated
the event. As such, it is good practise to ensure cache listener implementations don't hold up the thread in
- long-running tasks. Alternatively, you could set the <literal>CacheListener.sync()</literal> attribute to
+ long-running tasks. Alternatively, you could set the <literal>CacheListener.sync</literal> attribute to
<literal>false</literal>, in which case you will not be notified in the caller's thread. See the
<xref linkend="element.listeners" /> on tuning this thread pool and size of blocking
queue.
Modified: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/configuration.xml
===================================================================
--- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/configuration.xml 2009-12-09 07:23:06 UTC (rev 8315)
+++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/configuration.xml 2009-12-10 04:47:19 UTC (rev 8316)
@@ -102,14 +102,15 @@
</para>
<programlisting role="JAVA"><![CDATA[
- Configuration config = new Configuration();
- config.setTransactionManagerLookupClass( GenericTransactionManagerLookup.class.getName() );
- config.setIsolationLevel(IsolationLevel.READ_COMMITTED);
- config.setCacheMode(CacheMode.LOCAL);
- config.setLockAcquisitionTimeout(15000);
+Configuration config = new Configuration();
+config.setTransactionManagerLookupClass(
+ GenericTransactionManagerLookup.class.getName() );
+config.setIsolationLevel(IsolationLevel.READ_COMMITTED);
+config.setCacheMode(CacheMode.LOCAL);
+config.setLockAcquisitionTimeout(15000);
- CacheFactory factory = new DefaultCacheFactory();
- Cache cache = factory.createCache(config);
+CacheFactory factory = new DefaultCacheFactory();
+Cache cache = factory.createCache(config);
]]></programlisting>
<para>
@@ -143,8 +144,8 @@
<literal>Configuration</literal>
class and its
<xref linkend="configuration.elements" />
- are all Java Beans that expose all config elements via simple setters
- and getters. Therefore, any good IOC framework such as Spring, Google Guice, JBoss Microcontainer, etc. should be able to
+ are all Java Beans that expose all configuration elements via simple setters
+ and getters. Therefore, any good IOC framework such as JBoss Microcontainer should be able to
build up a
<literal>Configuration</literal>
from an XML file in
@@ -177,7 +178,7 @@
<para>
Following is a brief overview of the components of a
<literal>Configuration</literal>
- . See the javadoc and the linked
+ . See the Javadoc and the linked
chapters in this book for a more complete explanation of the
configurations associated with each component.
@@ -299,7 +300,7 @@
<section id="configuration.options">
<title>Overriding the Configuration via the Option API</title>
<para>
- The Option API allows you to override certain behaviours of the cache on a per invocation basis.
+ The Option API allows you to override certain behaviors of the cache on a per invocation basis.
This involves creating an instance of
<literal>org.jboss.cache.config.Option</literal>
, setting the options
@@ -330,7 +331,7 @@
node.put("localCounter", new Integer(2));
]]></programlisting>
<para>
- See the javadocs on the
+ See the Javadocs on the
<literal>Option</literal>
class for details on the options available.
</para>
Modified: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/deployment.xml
===================================================================
--- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/deployment.xml 2009-12-09 07:23:06 UTC (rev 8315)
+++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/deployment.xml 2009-12-10 04:47:19 UTC (rev 8316)
@@ -28,7 +28,7 @@
<para>
After creation, you could share your cache instance among different application components either by using an
- IOC container such as Spring, JBoss Microcontainer, etc., or by binding it to JNDI, or simply
+ IOC container such as JBoss Microcontainer, or by binding it to JNDI, or simply
holding a static reference to the cache.
</para>
@@ -140,7 +140,7 @@
]]></programlisting>
<para>
- See <ulink url="http://www.jboss.org/jbossmc/docs">the JBoss Microcontainer documentation</ulink>
+ See <ulink url="http://www.jboss.org/jbossmc">the JBoss Microcontainer documentation</ulink>
for details on the above syntax. Basically, each
<literal>bean</literal>
element represents an object and is used to create a
@@ -198,7 +198,7 @@
cache has already been started.</para>
</listitem>
</itemizedlist>
- See the <literal>CacheJmxWrapperMBean</literal> javadoc for more details.
+ See the <literal>CacheJmxWrapperMBean</literal> Javadoc for more details.
</para>
<para>
If a <literal>CacheJmxWrapper</literal> is registered, JBoss Cache also provides MBeans
@@ -219,11 +219,8 @@
deploying your cache.
</para>
- <section id="jmx.registration.programatic">
- <title>Programatic Registration</title>
-
<section id="jmx.registration.programatic.construct">
- <title>With a Cache instance</title>
+ <title>Programatic Registration with a Cache instance</title>
<para>
Simplest way to do this is to create your <literal>Cache</literal> and pass it to the
<literal>JmxRegistrationManager</literal> constructor.
@@ -252,7 +249,7 @@
</section>
<section id="jmx.registration.programatic.cfg">
- <title>With a Configuration instance</title>
+ <title>Programatic Registration with a Configuration instance</title>
<para>
Alternatively, build a <literal>Configuration</literal> object and pass it to the
<literal>CacheJmxWrapper</literal>. The wrapper will construct the <literal>Cache</literal> on your
@@ -282,7 +279,6 @@
wrapper.destroy();
]]></programlisting>
</section>
- </section>
<section>
<title>JMX-Based Deployment in JBoss AS (JBoss AS 5.x)</title>
@@ -395,7 +391,7 @@
<para>
If a <literal>CacheJmxWrapper</literal> is registered with JMX, the wrapper also ensures that
an MBean is registered in JMX for each interceptor and component that exposes statistics.
- <footnote>
+ <note>
<para>
Note that if the
<literal>CacheJmxWrapper</literal>
@@ -408,7 +404,7 @@
that this sort of "discovery" of the JMX environment was beyond the proper scope of
a caching library, so we removed this functionality.
</para>
- </footnote>.
+ </note>.
Management tools can then access those MBeans to examine the statistics. See the section in the
<xref linkend="jmx_reference.statistics" />
pertaining to the statistics that are made available via JMX.
14 years, 5 months
- 1
- 0
JBoss Cache SVN: r8315 - in enterprise-docs/tags: JBoss_EWP_5_0_0/Cache_User_Guide/en-US and 1 other directory.
by jbosscache-commits＠lists.jboss.org
Author: laubai
Date: 2009-12-09 02:23:06 -0500 (Wed, 09 Dec 2009)
New Revision: 8315
Modified:
enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/introduction.xml
enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/introduction.xml
Log:
Changes to introduction of Cache User Guide for JBPAPP-2964.
Modified: enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/introduction.xml
===================================================================
--- enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/introduction.xml 2009-12-07 09:26:19 UTC (rev 8314)
+++ enterprise-docs/tags/JBoss_EAP_5_0_0/Cache_User_Guide/en-US/introduction.xml 2009-12-09 07:23:06 UTC (rev 8315)
@@ -25,18 +25,18 @@
cluster services such as HTTP and <ulink url="http://java.sun.com/products/ejb/">EJB</ulink> sessions, as well as
providing a distributed entity cache for <ulink url="http://en.wikipedia.org/wiki/Java_Persistence_API">JPA</ulink>.
</para>
- <para>
+ <!--<para>
JBoss Cache can - and often is - used outside of JBoss AS, in other Java EE environments such as Spring, Tomcat,
Glassfish, BEA WebLogic, IBM WebSphere, and even in standalone Java programs thanks to its minimal dependency set.
- </para>
+ </para>-->
<section>
<title>And what is POJO Cache?</title>
<para>
POJO Cache is an extension of the core JBoss Cache API. POJO Cache offers additional functionality such as:
<itemizedlist>
- <listitem><para>maintaining object references even after replication or persistence.</para></listitem>
- <listitem><para>fine grained replication, where only modified object fields are replicated.</para></listitem>
- <listitem><para>"API-less" clustering model where POJOs are simply annotated as being clustered.</para></listitem>
+ <listitem><para>maintaining object references even after replication or persistence</para></listitem>
+ <listitem><para>fine grained replication, where only modified object fields are replicated</para></listitem>
+ <listitem><para>"API-less" clustering model where POJOs are simply annotated as being clustered</para></listitem>
</itemizedlist>
</para>
<para>
@@ -58,10 +58,10 @@
JBoss Cache offers a simple and straightforward API, where data - simple Java objects - can be placed in the
cache. Based on configuration options selected, this data may be one or all of:
<itemizedlist>
- <listitem><para>cached in-memory for efficient, thread-safe retrieval.</para></listitem>
- <listitem><para>replicated to some or all cache instances in a cluster.</para></listitem>
- <listitem><para>persisted to disk and/or a remote, in-memory cache cluster ("far-cache").</para></listitem>
- <listitem><para>garbage collected from memory when memory runs low, and passivated to disk so state isn't lost.</para>
+ <listitem><para>cached in-memory for efficient, thread-safe retrieval</para></listitem>
+ <listitem><para>replicated to some or all cache instances in a cluster</para></listitem>
+ <listitem><para>persisted to disk and/or a remote, in-memory cache cluster ("far-cache")</para></listitem>
+ <listitem><para>garbage collected from memory when memory runs low, and passivated to disk so state isn't lost</para>
</listitem>
</itemizedlist>
In addition, JBoss Cache offers a rich set of enterprise-class features:
@@ -153,7 +153,7 @@
JBoss Cache requires a Java 5.0 (or newer) compatible virtual machine and set of libraries, and is developed
and tested on Sun's JDK 5.0 and JDK 6.
</para>
- <para>
+ <!--<para>
There is a way to build JBoss Cache as a Java 1.4.x compatible binary using
<ulink url="http://www.jboss.org/community/docs/DOC-10738">JBossRetro</ulink>
to retroweave the Java 5.0 binaries. However, Red Hat Inc. does not offer professional support around the
@@ -162,7 +162,7 @@
<ulink url="http://www.jboss.org/community/docs/DOC-10263">this wiki</ulink>
page for
details on building the retroweaved binary for yourself.
- </para>
+ </para>-->
<para>
In addition to Java 5.0, at a minimum, JBoss Cache has dependencies on
<ulink url="http://www.jgroups.org">JGroups</ulink>, and Apache's
@@ -175,7 +175,7 @@
<title>License</title>
<para>
JBoss Cache is an open source project, using the business and OEM-friendly
- <ulink url="http://www.opensource.org/">OSI-approved</ulink>
+ <ulink url="http://www.opensource.org/">OSI-approved</ulink>
<ulink url="http://www.gnu.org/copyleft/lesser.html">LGPL license.</ulink>
Commercial development support, production support and training for JBoss Cache is available through
<ulink url="http://www.jboss.com">JBoss, a division of Red Hat Inc.</ulink>
Modified: enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/introduction.xml
===================================================================
--- enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/introduction.xml 2009-12-07 09:26:19 UTC (rev 8314)
+++ enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/introduction.xml 2009-12-09 07:23:06 UTC (rev 8315)
@@ -25,18 +25,18 @@
cluster services such as HTTP and <ulink url="http://java.sun.com/products/ejb/">EJB</ulink> sessions, as well as
providing a distributed entity cache for <ulink url="http://en.wikipedia.org/wiki/Java_Persistence_API">JPA</ulink>.
</para>
- <para>
+ <!--<para>
JBoss Cache can - and often is - used outside of JBoss AS, in other Java EE environments such as Spring, Tomcat,
Glassfish, BEA WebLogic, IBM WebSphere, and even in standalone Java programs thanks to its minimal dependency set.
- </para>
+ </para>-->
<section>
<title>And what is POJO Cache?</title>
<para>
POJO Cache is an extension of the core JBoss Cache API. POJO Cache offers additional functionality such as:
<itemizedlist>
- <listitem><para>maintaining object references even after replication or persistence.</para></listitem>
- <listitem><para>fine grained replication, where only modified object fields are replicated.</para></listitem>
- <listitem><para>"API-less" clustering model where POJOs are simply annotated as being clustered.</para></listitem>
+ <listitem><para>maintaining object references even after replication or persistence</para></listitem>
+ <listitem><para>fine grained replication, where only modified object fields are replicated</para></listitem>
+ <listitem><para>"API-less" clustering model where POJOs are simply annotated as being clustered</para></listitem>
</itemizedlist>
</para>
<para>
@@ -58,10 +58,10 @@
JBoss Cache offers a simple and straightforward API, where data - simple Java objects - can be placed in the
cache. Based on configuration options selected, this data may be one or all of:
<itemizedlist>
- <listitem><para>cached in-memory for efficient, thread-safe retrieval.</para></listitem>
- <listitem><para>replicated to some or all cache instances in a cluster.</para></listitem>
- <listitem><para>persisted to disk and/or a remote, in-memory cache cluster ("far-cache").</para></listitem>
- <listitem><para>garbage collected from memory when memory runs low, and passivated to disk so state isn't lost.</para>
+ <listitem><para>cached in-memory for efficient, thread-safe retrieval</para></listitem>
+ <listitem><para>replicated to some or all cache instances in a cluster</para></listitem>
+ <listitem><para>persisted to disk and/or a remote, in-memory cache cluster ("far-cache")</para></listitem>
+ <listitem><para>garbage collected from memory when memory runs low, and passivated to disk so state isn't lost</para>
</listitem>
</itemizedlist>
In addition, JBoss Cache offers a rich set of enterprise-class features:
@@ -153,7 +153,7 @@
JBoss Cache requires a Java 5.0 (or newer) compatible virtual machine and set of libraries, and is developed
and tested on Sun's JDK 5.0 and JDK 6.
</para>
- <para>
+ <!--<para>
There is a way to build JBoss Cache as a Java 1.4.x compatible binary using
<ulink url="http://www.jboss.org/community/docs/DOC-10738">JBossRetro</ulink>
to retroweave the Java 5.0 binaries. However, Red Hat Inc. does not offer professional support around the
@@ -162,7 +162,7 @@
<ulink url="http://www.jboss.org/community/docs/DOC-10263">this wiki</ulink>
page for
details on building the retroweaved binary for yourself.
- </para>
+ </para>-->
<para>
In addition to Java 5.0, at a minimum, JBoss Cache has dependencies on
<ulink url="http://www.jgroups.org">JGroups</ulink>, and Apache's
@@ -175,7 +175,7 @@
<title>License</title>
<para>
JBoss Cache is an open source project, using the business and OEM-friendly
- <ulink url="http://www.opensource.org/">OSI-approved</ulink>
+ <ulink url="http://www.opensource.org/">OSI-approved</ulink>
<ulink url="http://www.gnu.org/copyleft/lesser.html">LGPL license.</ulink>
Commercial development support, production support and training for JBoss Cache is available through
<ulink url="http://www.jboss.com">JBoss, a division of Red Hat Inc.</ulink>
14 years, 5 months
- 1
- 0
JBoss Cache SVN: r8314 - pojo/trunk/src/test/java/org/jboss/cache/pojo/passivation.
by jbosscache-commits＠lists.jboss.org
Author: galder.zamarreno(a)jboss.com
Date: 2009-12-07 04:26:19 -0500 (Mon, 07 Dec 2009)
New Revision: 8314
Modified:
pojo/trunk/src/test/java/org/jboss/cache/pojo/passivation/LocalTest.java
Log:
Added @NodeEvicted callback checks.
Modified: pojo/trunk/src/test/java/org/jboss/cache/pojo/passivation/LocalTest.java
===================================================================
--- pojo/trunk/src/test/java/org/jboss/cache/pojo/passivation/LocalTest.java 2009-12-04 06:38:43 UTC (rev 8313)
+++ pojo/trunk/src/test/java/org/jboss/cache/pojo/passivation/LocalTest.java 2009-12-07 09:26:19 UTC (rev 8314)
@@ -18,6 +18,7 @@
import org.jboss.cache.Fqn;
import org.jboss.cache.notifications.annotation.CacheListener;
import org.jboss.cache.notifications.annotation.NodeActivated;
+import org.jboss.cache.notifications.annotation.NodeEvicted;
import org.jboss.cache.notifications.annotation.NodePassivated;
import org.jboss.cache.notifications.event.NodeEvent;
import org.jboss.cache.pojo.PojoCache;
@@ -84,7 +85,7 @@
private void sanityCheck()
{
- if (listener_.getActivationCount() == 0 || listener_.getPassivationCount() == 0)
+ if (listener_.getActivationCount() == 0 || listener_.getPassivationCount() == 0 || listener_.eviction == 0)
{
fail("Sanity checking for passivation failed. Counters: activation - " + listener_.getActivationCount()
+ " passivation - " + listener_.getPassivationCount());
@@ -248,6 +249,7 @@
{
int activation = 0;
int passivation = 0;
+ int eviction = 0;
public int getActivationCount()
{
@@ -285,5 +287,15 @@
passivation++;
}
}
+
+ @NodeEvicted
+ public void nodeEvicted(NodeEvent ne)
+ {
+ if (!ne.isPre())
+ {
+ System.out.println("nodeEvicted: " + ne.getFqn());
+ eviction++;
+ }
+ }
}
}
14 years, 5 months
- 1
- 0