Spring/spring-session-data-geode
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove optional 'gemfire.log-level' System property from command-line.

Browse Source
This commit is contained in:
John Blum
2018-08-20 21:53:11 -07:00
parent e1b5b1c5b5
commit c0c3ade687
5 changed files with 9 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/src/docs/asciidoc/guides/boot-gemfire.adoc
View File

@@ -175,13 +175,13 @@ You can run the sample by obtaining the {download-url}[source code] and invoking
First, you must run the server:
----
$ ./gradlew :spring-session-sample-boot-gemfire:run [-Dgemfire.log-level=config]
$ ./gradlew :spring-session-sample-boot-gemfire:run
----
Then, in a separate terminal, run the client:
----
$ ./gradlew :spring-session-sample-boot-gemfire:bootRun [-Dgemfire.log-level=config]
$ ./gradlew :spring-session-sample-boot-gemfire:bootRun
----
You should now be able to access the application at http://localhost:8080/.

7
docs/src/docs/asciidoc/guides/java-gemfire-clientserver.adoc
View File

@@ -191,19 +191,18 @@ You can run the sample by obtaining the {download-url}[source code] and invoking
First, you need to run the server using:
----
$ ./gradlew :spring-session-sample-javaconfig-gemfire-clientserver:run [-gemfire.log-level=info]
$ ./gradlew :spring-session-sample-javaconfig-gemfire-clientserver:run
----
Then, in a separate terminal, run the client using:
----
$ ./gradlew :spring-session-sample-javaconfig-gemfire-clientserver:tomcatRun [-gemfire.log-level=info]
$ ./gradlew :spring-session-sample-javaconfig-gemfire-clientserver:tomcatRun
----
You should now be able to access the application at http://localhost:8080/.
In this sample, the web application is the Apache Geode cache client
and the server is standalone, separate (JVM) process.
In this sample, the web application is the Apache Geode cache client and the server is standalone, separate JVM process.
=== Exploring the httpsession-gemfire-clientserver Sample Application

2
docs/src/docs/asciidoc/guides/java-gemfire-p2p.adoc
View File

@@ -148,7 +148,7 @@ our `Config` class.
You can run the sample by obtaining the {download-url}[source code] and invoking the following command:
----
$ ./gradlew :spring-session-sample-javaconfig-gemfire-p2p:tomcatRun [-Dgemfire.log-level=info]
$ ./gradlew :spring-session-sample-javaconfig-gemfire-p2p:tomcatRun
----
You should now be able to access the application at http://localhost:8080/.

4
docs/src/docs/asciidoc/guides/xml-gemfire-clientserver.adoc
View File

@@ -190,13 +190,13 @@ You can run the sample by obtaining the {download-url}[source code] and invoking
First, you need to run the server using:
----
$ ./gradlew :spring-session-sample-javaconfig-gemfire-clientserver:run [-Dgemfire.log-level=info]
$ ./gradlew :spring-session-sample-javaconfig-gemfire-clientserver:run
----
Now, in a separate terminal, you can run the client using:
----
$ ./gradlew :spring-session-sample-javaconfig-gemfire-clientserver:tomcatRun [-gemfire.log-level=info]
$ ./gradlew :spring-session-sample-javaconfig-gemfire-clientserver:tomcatRun
----
You should now be able to access the application at http://localhost:8080/.

2
docs/src/docs/asciidoc/guides/xml-gemfire-p2p.adoc
View File

@@ -140,7 +140,7 @@ the `DelegatingFilterProxy` is invoked, delegating to the `springSessionReposito
You can run the sample by obtaining the {download-url}[source code] and invoking the following command:
----
$ ./gradlew :spring-session-sample-xml-gemfire-p2p:tomcatRun [-Dgemfire.log-level=info]
$ ./gradlew :spring-session-sample-xml-gemfire-p2p:tomcatRun
----
You should now be able to access the application at http://localhost:8080/.