Initial implementation and tests for JIRA feature requests SGF-207 and SGF-254 supporting inheritable Region templates when defining GemFire Regions using Spring Data GemFire XML configuration meta-data.  This feature allows common Region configuration and attribute values to be defined once and then shared across multiple Region bean definitions in the Spring context for added convenience.
Additional work and changes for JIRA feature requests SGF-207 and SGF-254 to enable developers with the ability to create Region templates to model attributes and configuration meta-data common to multiple, strongly-typed GemFire Region types (e.g. REPLICATE, PARTITION, etc).
Code refactoring and cleanup related to SGF-207 and SGF-254, Region Templates.
Completed Peer Cache Region Template testing for JIRA feature requests SGF-207 and SGF-254 adding support for template-defined Regions.
Added another test case for JIRA feature requests SGF-207 and SDG-254, Region Templates, to test the correct Region to Region Template bean defintion order in the Spring context configuration file.  Region Templates must be defined 'before' the Regions that are based on those template definitions.
Completed Client Cache Region Template testing for JIRA feature requests SGF-207 and SGF-254 adding support for template-defined Regions.  In addition, fixed JIRA bug SGF-310 pertaining to the missing 'concurrency-level' attribute on the <gfe:client-region> element in the SDG XSD as well as SGF-311 involving the ClientRegionFactoryBean not properly setting the 'concurrencyChecksEnabled' property on GemFire's ClientRegionFactory class.
Added additional test case to test Client Region attribute configuration settings, including the new attributes for concurrency (concurrency-checks-enabled and concurrency-level) for SGF-310 and SGF-311.
Refactored and fixed failing test cases after the integration of SGF-207, SGF-254, SGF-307, SGF-309, SGF-310, SGF-311 and SGF-312.