Spring Data GemFire 1.3.0 是 Spring Data 项目中用于简化 Apache Geode（原 GemFire）集成的一个版本

Spring Data GemFire 1.3.0 是 Spring Data 项目中用于简化 Apache Geode原 GemFire集成的一个版本于 2014 年左右发布具体为 2014 年 8 月标志着对 Pivotal GemFire 7.x/8.x 的增强支持并引入了多项改进与新特性包括更完善的 Repository 抽象支持如Query注解、派生查询方法对 GemFire 8.x 新特性的适配如 Continuous Query 支持、Region Subregion 查询优化增强的配置模型JavaConfig 优先XML 配置兼容改进的事务管理支持Transactional与 GemFire 本地事务更好的错误处理与日志可观察性移除过时 API提升与 Spring Framework 4.x 的兼容性⚠️ 注意GemFire 已于 2015 年由 Pivotal 开源并演进为 Apache GeodeSpring Data GemFire 后续版本逐步过渡为 Spring Data GeodeSDG官方推荐新项目使用 Spring Data Geode 替代。!-- Maven 依赖示例已过时仅作历史参考 --dependencygroupIdorg.springframework.data/groupIdartifactIdspring-data-gemfire/artifactIdversion1.3.0.RELEASE/version/dependencySpring Data GemFire 1.3.0 ReleasedI am pleased to announce the GA release of Spring Data GemFire 1.3.0. In addition to many minor bug fixes and enhancements, this release includes some notable new features to make writing Java applications with GemFire even easier:Annotation Support For FunctionsGemFire provides the ability to “bring the code to the data” by providing a framework for remote function execution. In keeping with Spring’s core values, Spring Data GemFire hides the boilerplate code necessary to register and execute remote functions, allowing you to write POJOs and focus on application logic. See the Annotation Support for Function Execution chapter in the Spring Data GemFire Reference Guide for details.Simplified Connection to a GemFire DatasourceGemFire exposes a lot of options for tuning the performance of it’s connection pool, and to configure how local data is managed an synchronized. The Spring Data GemFire namespace supports all of these options, however many applications are clients that simply need read/write access to the GemFire data grid. For this class of applications, it is now possible to connect to GemFire as a client without explicitly configuring a pool or client regions:gfe-data:datasourcegfe-data:locator host“hostport{host} porthostport{port}”//gfe-data:datasourceThe above configuration will create a client cache, pool, and proxy client regions for all available regions on the server, with sensible defaults, and register them as Spring beans.JSON SupportGemFire 7.0 provides the ability to store JSON with full query support. Typically this requires the application to use the JSONFormatter to convert GemFire’s internal format to and from JSON Strings. Spring Data GemFire now provides an option to perform this conversion automatically for selected regions, as will as one way conversion from Object to JSON using Jackson’s ObjectMapper. This feature uses Spring AOP to intercept appropriate operations on Region and GemFireTemplate. See the Spring Data GemFire Reference Guide for details.comments powered by Disqus