John Blum

Unfortunately, and currently, there are test conflicts due to stale state in the test JVM, either in Apache Geode or the Spring `ApplicationContext`. ``` [INFO] Results: [INFO] [ERROR] Failures: [ERROR]...

To confirm the 3 different methods for the configuration of collocated `PARTITION` _Regions_ using SDG, I added new test classes / test cases and modified existing ones to confirm the...

Next, I explored the use of _Spring JavaConfig_ using the SDG API, and specifically the [`PartitionedRegionFactoryBean`](https://docs.spring.io/spring-data/geode/docs/current/api/org/springframework/data/gemfire/PartitionedRegionFactoryBean.html) class, [`RegionAttributesFactoryBean`](https://docs.spring.io/spring-data/geode/docs/current/api/org/springframework/data/gemfire/RegionAttributesFactoryBean.html) class and [`PartitionAttributesFactoryBean`](https://docs.spring.io/spring-data/geode/docs/current/api/org/springframework/data/gemfire/PartitionAttributesFactoryBean.html) class. Again, these SDG API classes were intentionally designed...

Finally, we explore the use of SDG's Annotation-based configuration model to create collocated `PARTITION` _Regions_ from application domain model, persistent entity classes. The test class is [here](https://github.com/spring-projects/spring-data-geode/blob/main/spring-data-geode/src/test/java/org/springframework/data/gemfire/config/annotation/EntityDefinedRegionsForRealCollocatedPartitionRegionsIntegrationTests.java), the test configuration...

I am not 100% for certain, but I think @yozaner1324 may have already fixed this issue. Need to verify.

This Issue ticket originated from _**Spring Boot for Apache Geode**_ (SBDG) [Issue #78](https://github.com/spring-projects/spring-boot-data-geode/issues/78) and is moving to _**Spring Data for Apache Geode**_ (SDG) for resolution.

A [prototype and POC](https://github.com/jxblum/contacts-application/tree/master/tests-example/src/test/java/example/tests/spring/data/geode/cache) of this solution has already been developed based on the requirements of a particular GemFire customer involving cache callbacks. Another GemFire customer has run into a...

It turns out, **Apache Geode** (and by extension, **Pivotal GemFire** & **Pivotal Cloud Cache** (PCC)) may very well delegate to the PDX serialization mechanics to serialize objects passed to `PdxWriter.writeObject(..)`....

Not all uses of internal Apache Geode APIs have been removed; this is a WIP!

This is exactly what I mean by "_Attached Sessions_" in Issue #13.