Browse files

updated docs for GemFire 7.0

  • Loading branch information...
1 parent cfdac73 commit 8c5fe281f8318a3dd5dc663cce6acd2bf33ce767 David Turanski committed Oct 26, 2012
+Changes in version 1.2.1.RELEASE (2012-10-26)
+* Upgraded to GemFire 7.0
+* Added support for GemFire 7.0 WAN Configuration
Changes in version 1.2.0.RELEASE (2012-08-15)
@@ -68,7 +68,7 @@
<para>In addition to referencing an external configuration file one can
specify GemFire <ulink
- url="">properties</ulink>
+ url="">properties</ulink>
using any of Spring's common properties support features. For example, one
can use the <literal>properties</literal> element defined in the
<literal>util</literal> namespace to define properties directly or load
@@ -142,19 +142,19 @@
<interfacename>TransactionListener</interfacename> callback
declaration using a bean reference. The referenced bean must implement
- url="">TransactionListener</ulink></para>
+ url="">TransactionListener</ulink></para>
<callout arearefs="gfe#transaction#writer">
<para>An example of a <interfacename>TransactionWriter</interfacename>
callback declaration using an inner bean declaration this time. The
bean must implement <ulink
- url="">TransactionWriter</ulink></para>
+ url="">TransactionWriter</ulink></para>
<callout arearefs="gfe#dynamic#region">
<para>Enable GemFire's <ulink
- url="">DynamicRegionFactory</ulink></para>
+ url="">DynamicRegionFactory</ulink></para>
<callout arearefs="gfe#jndi#binding">
@@ -205,7 +205,7 @@
<para>In Spring Data GemFire 1.1 dedicated support for configuring a
- url="">CacheServer</ulink>
+ url="">CacheServer</ulink>
was added, allowing complete configuration through the Spring
@@ -276,7 +276,7 @@
<para>Another configuration addition in Spring Data GemFire 1.1 is the
dedicated support for configuring <ulink
- url="">ClientCache</ulink>.
+ url="">ClientCache</ulink>.
This is similar to a <link linkend="bootstrap:cache">cache</link> in both
usage and definition and supported by
@@ -310,5 +310,5 @@
<para>Client side configuration is covered in more detail in <xref
- linkend="bootstrap:client"/>.</para>
+ linkend="bootstrap:region:client"/>.</para>
@@ -47,7 +47,7 @@
<para>The <classname>ContinuousQueryListenerAdapter</classname> class is the
final component in Spring Data GemFire CQ support: in a nutshell, it allows you to expose almost <emphasis>any</emphasis> class
as a EDP (there are of course some constraints) - it implements <interfacename>ContinuousQueryListener</interfacename>, a simpler listener interface
- similar to GemFire <ulink url="">CqListener</ulink>.</para>
+ similar to GemFire <ulink url="">CqListener</ulink>.</para>
<para>Consider the following interface definition. Notice the
various event handling methods and their parameters:</para>
@@ -120,7 +120,7 @@
through the <literal>copyOnRead</literal> property. For more information
on the semantics of the underlying GemFire transaction manager, see the
GemFire <ulink
- url="">documentation</ulink>.</para>
+ url="">documentation</ulink>.</para>
<xi:include href="cq-container.xml"/>
@@ -53,7 +53,7 @@
<para>For more information about the various region types and their
capabilities as well as configuration options, please refer to the GemFire
Developer's <ulink
- url="">Guide</ulink>
+ url="">Guide</ulink>
and community <ulink
@@ -118,7 +118,7 @@
<para>Client Region <literal>&lt;client-region&gt;</literal></para>
</itemizedlist>For a comprehensive description of <ulink
- url="">region
+ url="">region
types</ulink> please consult the GemFire product documentation.</para>
<section id="bootstrap:region:common:attributes">
@@ -175,7 +175,7 @@
<entry spanname="values">
<emphasis>See GemFire's <ulink
- url="">Data
+ url="">Data
@@ -354,7 +354,7 @@
<para>Cache Listeners are registered with a region to handle region
events such as entries being created, updated, destroyed, etc. A Cache
Listener can be any bean that implements the <ulink
- url="">
+ url="">
</ulink> interface. A region may have multiple listeners, declared
using the <literal>cache-listener</literal> element enclosed in a
@@ -426,10 +426,10 @@
source. The difference is GemFire only supports at most a single
instance of each for each region. However, either declaration style may
be used. See <ulink
- url="">
+ url="">
</ulink> and <ulink
- url="">
+ url="">
</ulink> for more details.</para>
@@ -535,7 +535,7 @@
<para>For a detailed description of eviction policies, see the GemFire
documentation (such as <ulink
- url="">this</ulink>
+ url="">this</ulink>
@@ -22,7 +22,7 @@
lives at a certain point in time, for example a DataSource. Serializing
such information is useless (and potentially even dangerous) since it is
local to a certain VM/machine. For such cases, Spring Data GemFire offers a special <ulink
- url=""><classname>Instantiator</classname></ulink>
+ url=""><classname>Instantiator</classname></ulink>
that performs wiring for each new instance created by GemFire during
@@ -31,7 +31,7 @@
from persistent data and have <emphasis>rich domain objects</emphasis> in
a transparent manner (Spring users might find this approach similar to
that of <ulink
- url=""><literal>@Configurable</literal></ulink>).
+ url=""><literal>@Configurable</literal></ulink>).
The <classname>WiringInstantiator</classname> works just like
<classname>WiringDeclarableSupport</classname>, trying to first locate a
bean definition as a wiring template and following to autowiring

0 comments on commit 8c5fe28

Please sign in to comment.