Github user PivotalSarge commented on a diff in the pull request:
https://github.com/apache/geode-native/pull/77#discussion_r108701675
--- Diff:
docs/geode-native-docs/cache-init-file/chapter-overview.html.md.erb ---
@@ -33,26 +33,23 @@ The initialization file can have any name, but is
generally referred to as `cach
The contents of a declarative XML file correspond to APIs declared in the
`Cache.hpp` and `Region.hpp` header files. The cache initialization file allows
you to accomplish declaratively many of the cache management activities that
you can program through the API.
-- The contents of the cache initialization file must conform to the XML
definition in <code>_product-dir_/dtd/gfcpp-cache8000.dtd</code>. The DTD file
identifies the valid element tags that may be present in your XML file, the
attributes that correspond to each element, and the valid values for the
elements and attributes.
-- The name of the declarative XML file is specified when establishing a
connection to the distributed system. You can define it by setting the
`cache-xml-file` configuration attribute in the `geode.properties` file for the
native client. For details about the `geode.properties` file, see [Setting
System and Cache Properties](../setting-properties/chapter-overview.html).
+- The contents of the cache initialization file must conform to the XML
definition in
[http://geode.apache.org/schema/cache/cache-1.0.xsd](http://geode.apache.org/schema/cache/cache-1.0.xsd).
This file identifies the valid element tags that may be present in your XML
file, the attributes that correspond to each element, and the valid values for
the elements and attributes.
+- The name of the declarative XML file is specified when establishing a
connection to the distributed system. You can define it by setting the
`cache-xml-file` configuration attribute in the `geode.properties` file for the
client. For details about the `geode.properties` file, see [Setting System and
Cache Properties](../setting-properties/chapter-overview.html).
# Example cache.xml File
An example `cache.xml` file shows cache and region initialization for a
client, presenting a subset of the possible data configurations.
-Specific information about cache and region attributes is in [Region
Attributes](../client-cache/region-attributes.html). Also check the API
documentation for `Cache` and `RegionAttributes` at
[http://gemfire-apis.docs.pivotal.io](http://gemfire-apis.docs.pivotal.io).
+Specific information about cache and region attributes is in [Region
Attributes](../client-cache/region-attributes.html).
-For information on using a cache with a server pool, see [Using Connection
Pools](../connection-pools/connection-pools.html). The example below shows a
`cache.xml` file that creates two regions.
-
-- Region `region1` is defined with a full set of region attributes and
application plug-ins. The region's entries have `RegionTimeToLive` and
`RegionIdleTimeout` expiration attributes set, as detailed in [Specifying
Expiration Attributes](../client-cache/expiration-attributes.html).
-- Region `region2` uses mostly default values.
+For information on using a cache with a server pool, see [Using Connection
Pools](../connection-pools/connection-pools.html). The example below shows a
`cache.xml` file that creates a region.
``` pre
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cache PUBLIC
- "-//Example Systems, Inc.//Example Declarative Caching 8.0//EN"
- "http://www.example.com/dtd/gfcpp-cache8000.dtd";>
+ "-//Example Systems, Inc.//Example Declarative Caching 1.0//EN"
+ "http://geode.apache.org/schema/cache/cache-1.0.xsd";>
--- End diff --
Nicely done.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
