From 822b2b9f524cfdbf3f1d7287c6730fa174c631ef Mon Sep 17 00:00:00 2001 From: David Turanski Date: Wed, 13 Feb 2013 09:04:15 -0500 Subject: [PATCH] Fixed formatting in data-access.xml --- docs/src/reference/docbook/reference/data-access.xml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/src/reference/docbook/reference/data-access.xml b/docs/src/reference/docbook/reference/data-access.xml index 122572ec..290cfd88 100644 --- a/docs/src/reference/docbook/reference/data-access.xml +++ b/docs/src/reference/docbook/reference/data-access.xml @@ -21,7 +21,7 @@ An Easy Way to Connect to GemFire For many applications, A basic connection to a GemFire grid, using - default values is sufficient. Spring Data GemFire's <datasource> tag + default values is sufficient. Spring Data GemFire's <datasource> tag provides a simple way to access data. The data source creates a client cache and connection pool. In addition, it will query the member servers for all existing root regions and create a proxy (empty) client region for @@ -31,17 +31,18 @@ <locator host="somehost" port="1234"/> </gfe-data:datasource> - The datasource tag is synactically similar to <gfe:pool>. + The datasource tag is synactically similar to <gfe:pool>. It may be configured with one or more locator or server tags to connect to an existing data grid. Additionally, all attributes available to configure a pool are supported. This configuration will automatically create ClientRegion beans for each region defined on members connected to the locator, so they may be seamlessly referenced by Spring Data mapping annotations, GemfireTemplate, and wired into application - classes. + classes. - Of course, you can explicitly configure client regions. For - example, if you want to cache data in local memory: Of course, you can explicitly configure client regions. For + example, if you want to cache data in local memory: + <gfe-data:datasource> <locator host="somehost" port="1234"/> </gfe-data:datasource>