The Pivotal GemFire Client/Server Example Applications project contains 4 individual modules with examples demonstrating the configuration of Pivotal GemFire client and server cache applications using both GemFire native cache.xml and GemFire's public Java API along with Spring Java-based Container Configuration and Spring (Data GemFire) XML Namespace configuration meta-data.
The module applications are broken down into the following examples:
| Example Application | Description |
|---|---|
| native-gemfire-clientserver-xml | Configures GemFire client/server using native cache.xml; Tests client/server connectivity and square root (x^1/2) operations. |
| native-gemfire-clientserver | Configures GemFire client/server using the Java API; Tests client/server connectivity and cubed (x^3) operations. |
| spring-gemfire-clientserver-xml | Configures GemFire client/server using the Spring (Data GemFire) XML namespace; Tests client/server connectivity and square root (x^1/2) operations. |
| spring-gemfire-clientserver | Configures GemFire client/server using Spring Java-based Container Configuration; Tests client/server connectivity and squared (x^2) operations. |
Drill into the individual modules for further details on how to build and run each example application.
- Java Development Kit (JDK) 1.8.0+ (e.g. 1.8.0_72).
- Apache Maven 3.3.x
Currently, the project is using Spring Data GemFire 1.8.5.RELEASE and Pivotal GemFire 8.2.0.
You can download distributions of the JDK here and Apache Maven at maven.apache.org.
To build this pivotal-gemfire-clientserver-examples project, run the following mvn command at the command-line
$ mvn clean install -DskipTests
You must skip tests when running the build since the project tests are technically integration tests. This means they require a GemFire (Cache) Server to be running in order to execute successfully.
For any issues or feedback with this project, please file a GitHub Issue.
I also welcome any contributions through Pull Requests. If you have an idea or improvement, please share. No CLA necessary.
Thanks