Note | |
---|---|
As of the 1.2.0 release, this project, formerly known as Spring GemFire, has been renamed to Spring Data GemFire to reflect that it is now a component of the Spring Data project. |
Full support for GemFire configuration via the SDG gfe namespace. Now GemFire components may be configured completely without requiring a native cache.xml file.
WAN Gateway support for GemFire 6.6.x. See Section 5.9, “Configuring WAN Gateways”.
Spring Data Repository support using a dedicated SDG namespace, gfe-data. See Chapter 9, GemFire Repositories
Namespace support for registering GemFire Functions. See Section 5.8, “Configuring GemFire's Function Service”
A top-level <disk-store>
element has been added to the SDG
gfe namespace to allow sharing of persist stores among Regions,
and other components that support persistent backup or overflow.
See Section 5.7, “Configuring a Disk Store”
Caution | |
---|---|
The <*-region> elements no longer allow a nested
<disk-store>
|
GemFire Sub-Regions are supported via nested <*-region>
elements.
A <local-region>
element has been added to configure a Local Region.
Annotation support for GemFire Functions. It is now possible to declare and register Functions written as POJOs using annotations. In addition, Function executions are defined as annotated interfaces, similar to the way Spring Data Repositories work. See Chapter 10, Annotation Support for Function Execution.
Added a <datasource>
element to the SDG gfe-data namespace to
simplify establishing a basic client connection
to a GemFire data grid.
Added a <json-region-autoproxy>
element to the SDG gfe-data
namespace to support JSON features introduced
in GemFire 7.0, enabling Spring AOP to perform the necessary conversions automatically
on Region operations.
Upgraded to GemFire 7.0.1 and added namespace support for new AsyncEventQueue attributes.
Added support for setting subscription interest policy on Regions.
Support for void returns on Function executions. See Chapter 10, Annotation Support for Function Execution for complete details.
Support for persisting Local Regions. See Section 5.5.8, “Local Region” and the section called “Common Region Attributes”.
Support for entry time-to-live and entry idle-time on a GemFire Client Cache. See Section 5.3.3, “Configuring a GemFire Client Cache”
Support for multiple Spring Data GemFire web-based applications using a single GemFire cluster, operating concurrently inside tc Server.
Support for concurrency-checks-enabled on all GemFire Cache Region definitions using the SDG gfe namespace. See the section called “Common Region Attributes”.
Support for Cache Loaders and Cache Writers on Client, Local Regions. See the section called “Cache Loaders and Cache Writers”.
Support for registering CacheListeners, AsyncEventQueues and Gateway Senders on GemFire Cache Sub-Regions.
Support for PDX persistent keys in GemFire Regions.
Support for correct Partition Region bean creation in a Spring context when collocation is specified with the colocated-with attribute.
Full support for GemFire Cache Sub-Regions using proper, nested <*-region>
element syntax in the SDG gfe namespace.
Upgraded Spring Data GemFire to Spring Framework 3.2.8.
Upgraded Spring Data GemFire to Spring Data Commons 1.7.1.
Upgrades Spring Data GemFire to GemFire 7.0.2.
Upgrades Spring Data GemFire to Spring Data Commons 1.8.0.
Integrates Spring Data GemFire with Spring Boot, which includes both a spring-boot-starter-data-gemfire POM along with a Spring Boot Sample application demonstrating GemFire Cache Transactions configured with SDG bootstrapped with Spring Boot.
Support for bootstrapping a Spring Context in a GemFire Server when started from Gfsh. See Chapter 11, Bootstrapping a Spring ApplicationContext in GemFire.
Support for persisting application domain object/entities to multiple GemFire Cache Regions. See Section 8.1, “Entity Mapping” for more details.
Support for persisting application domain object/entities to GemFire Cache Sub-Regions, avoiding collisions when Sub-Regions are uniquely identifiable, but identically named. See Section 8.1, “Entity Mapping” for more details.
Adds strict XSD type rules to, and full support for, Data Policies and Region Shortcuts on all GemFire Cache Region types.
Changed the default behavior of SDG <*-region>
elements from lookup
to always create a new Region along with an option to restore old behavior using the
ignore-if-exists attribute.
See Common Region Attributes
and Section 5.5.3, “A Word of Caution on Regions, Subregions and Lookups”
for more details.
Enables Spring Data GemFire to be fully built and ran on JDK 7 and JDK 8 (Note, however, GemFire has not yet been fully tested and supported on JDK 8; See GemFire User Guide for additional details.