You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by rv...@apache.org on 2016/09/30 00:33:08 UTC
[01/50] [abbrv] incubator-geode git commit: Change , to >
Repository: incubator-geode
Updated Branches:
refs/staging/docs-grant1 [created] 2eabdb2d7
Change , to >
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/1218f209
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/1218f209
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/1218f209
Branch: refs/staging/docs-grant1
Commit: 1218f2092019294bc76ad7b0220e0eb6170497f3
Parents: 839082e
Author: Joey McAllister <jm...@pivotal.io>
Authored: Wed Aug 31 09:41:07 2016 -0700
Committer: Joey McAllister <jm...@pivotal.io>
Committed: Wed Aug 31 09:41:07 2016 -0700
----------------------------------------------------------------------
.../client-cache-elements-list.html.md.erb | 24 +++++++++-----------
1 file changed, 11 insertions(+), 13 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/1218f209/reference/topics/client-cache-elements-list.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/client-cache-elements-list.html.md.erb b/reference/topics/client-cache-elements-list.html.md.erb
index d5d4a24..2b533cc 100644
--- a/reference/topics/client-cache-elements-list.html.md.erb
+++ b/reference/topics/client-cache-elements-list.html.md.erb
@@ -24,7 +24,7 @@ For details, see [<client-cache> Element Reference.](client-cache.html)
<string>
<declarable>
<region-attributes>
- <key-constraint>
+ <key-constraint>
<value-constraint>
<region-time-to-live>
<expiration-attributes>
@@ -33,19 +33,19 @@ For details, see [<client-cache> Element Reference.](client-cache.html)
<parameter>
<string>
<declarable>
- <region-idle-time>
+ <region-idle-time>
<expiration-attributes>
<custom-expiry>
<class-name>
<parameter>
<string>
<declarable>
- <entry-time-to-live>
+ <entry-time-to-live>
<expiration-attributes>
<custom-expiry>
<class-name>
<parameter>
- <string.
+ <string>
<declarable>
<entry-idle-time>
<expiration-attributes>
@@ -54,17 +54,17 @@ For details, see [<client-cache> Element Reference.](client-cache.html)
<parameter>
<string>
<declarable>
- <cache-loader>
+ <cache-loader>
<class-name>
<parameter>
<string>
<declarable>
- <cache-writer>
+ <cache-writer>
<class-name>
<parameter>
<string>
<declarable>
- <cache-listener>
+ <cache-listener>
<class-name>
<parameter>
<string>
@@ -89,7 +89,7 @@ For details, see [<client-cache> Element Reference.](client-cache.html)
<config-property-value>
<region>
<region-attributes>
- <index>
+ <index>
<entry>
<key>
<string>
@@ -97,7 +97,7 @@ For details, see [<client-cache> Element Reference.](client-cache.html)
<value>
<string>
<declarable>
- <region>
+ <region>
<function-service>
<function>
<class-name>
@@ -109,14 +109,12 @@ For details, see [<client-cache> Element Reference.](client-cache.html)
<serializer>
<class-name>
<instantiator>
- <class-name>
+ <class-name>
<initializer>
<class-name>
<parameter>
<string>
<declarable>
</client-cache>
-
-```
-
+```
[14/50] [abbrv] incubator-geode git commit: Merge remote-tracking
branch 'origin/develop' into feature/IntegratedSecurity
Posted by rv...@apache.org.
Merge remote-tracking branch 'origin/develop' into feature/IntegratedSecurity
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/0ce38b13
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/0ce38b13
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/0ce38b13
Branch: refs/staging/docs-grant1
Commit: 0ce38b13ecc3e2fe708a64c7c4754ec6b52a0b46
Parents: 37d050c 51f43fa
Author: Karen Miller <km...@pivotal.io>
Authored: Tue Sep 6 15:06:02 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Tue Sep 6 15:06:02 2016 -0700
----------------------------------------------------------------------
----------------------------------------------------------------------
[30/50] [abbrv] incubator-geode git commit: Updated supported
versions for Tomcat and tc Server. [#129957543]
Posted by rv...@apache.org.
Updated supported versions for Tomcat and tc Server. [#129957543]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/66a81e89
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/66a81e89
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/66a81e89
Branch: refs/staging/docs-grant1
Commit: 66a81e89d63e4508b51eb0306e3ef74b52e2bf04
Parents: f38a81a
Author: Karen Miller <km...@pivotal.io>
Authored: Tue Sep 13 15:34:20 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Tue Sep 13 15:34:20 2016 -0700
----------------------------------------------------------------------
tools_modules/http_session_mgmt/quick_start.html.md.erb | 7 +++----
.../http_session_mgmt/tc_installing_the_module.html.md.erb | 2 +-
2 files changed, 4 insertions(+), 5 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/66a81e89/tools_modules/http_session_mgmt/quick_start.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/http_session_mgmt/quick_start.html.md.erb b/tools_modules/http_session_mgmt/quick_start.html.md.erb
index b349bb8..007621a 100644
--- a/tools_modules/http_session_mgmt/quick_start.html.md.erb
+++ b/tools_modules/http_session_mgmt/quick_start.html.md.erb
@@ -10,9 +10,8 @@ In this section you download, install, and set up the HTTP Session Management mo
| Supported Application Server | Version | Download Location |
|------------------------------|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
- | tc Server | 2.9, 2.8, 2.7, 2.6, and 2.5 | [https://my.vmware.com/web/vmware/info/slug/application_platform/vmware_vfabric_tc_server/2_9](https://my.vmware.com/web/vmware/info/slug/application_platform/vmware_vfabric_tc_server/2_8) |
+ | tc Server | 2.9 (Deprecated) | [https://my.vmware.com/web/vmware/info/slug/application_platform/vmware_vfabric_tc_server/2_9](https://my.vmware.com/web/vmware/info/slug/application_platform/vmware_vfabric_tc_server/2_9) |
| tc Server | 3.0 and 3.1 | [https://network.pivotal.io/products/pivotal-tcserver](https://network.pivotal.io/products/pivotal-tcserver) |
- | Tomcat | 6.0 | [http://tomcat.apache.org/download-60.cgi](http://tomcat.apache.org/download-60.cgi) |
| Tomcat | 7.0 | [http://tomcat.apache.org/download-70.cgi](http://tomcat.apache.org/download-70.cgi) |
| Tomcat | 8.0 | [http://tomcat.apache.org/download-80.cgi](http://tomcat.apache.org/download-80.cgi) |
| WebLogic | 11g (10.3.x) | [http://www.oracle.com/technetwork/middleware/weblogic/overview/index.html](http://www.oracle.com/technetwork/middleware/weblogic/overview/index.html) |
@@ -25,9 +24,9 @@ In this section you download, install, and set up the HTTP Session Management mo
| Supported Application Server | Version | Module | Target Location for Module |
|------------------------------|-----------------------------|----------------------------------------------------------|----------------------------------------------------------------------------------|
- | tc Server | 2.5, 2.6, 2.7, 2.8, and 2.9 | HTTP Session Management Module for Pivotal tc Server | `<tc Server root dir>/templates` |
+ | tc Server | 2.9 (Deprecated) | HTTP Session Management Module for Pivotal tc Server | `<tc Server root dir>/templates` |
| tc Server | 3.0 | HTTP Session Management Module for Pivotal tc Server 3.0 | `<tc Server root dir>/templates` |
- | Tomcat | 6.0 and 7.0 | HTTP Session Management Module for Tomcat | `$CATALINA_HOME` |
+ | Tomcat | 7.0 | HTTP Session Management Module for Tomcat | `$CATALINA_HOME` |
| WebLogic | 11g (10.3.x) | HTTP Session Management Module for AppServers | *any directory* |
| WebSphere | 7, 8 | HTTP Session Management Module for AppServers | *any directory* |
| JBoss | 5, 6, 7 | HTTP Session Management Module for AppServers | *any directory* |
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/66a81e89/tools_modules/http_session_mgmt/tc_installing_the_module.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/http_session_mgmt/tc_installing_the_module.html.md.erb b/tools_modules/http_session_mgmt/tc_installing_the_module.html.md.erb
index 990aee4..d8acf4d 100644
--- a/tools_modules/http_session_mgmt/tc_installing_the_module.html.md.erb
+++ b/tools_modules/http_session_mgmt/tc_installing_the_module.html.md.erb
@@ -4,7 +4,7 @@ title: Installing the HTTP Module for tc Server
This topic describes how to install the HTTP session management module with tc Server templates.
-1. If you do not already have tc Server, download and install the product from the [VMware tc Server download page](https://my.vmware.com/web/vmware/info/slug/application_platform/vmware_vfabric_tc_server/2_9) or the [Pivotal tc Server download page](https://network.pivotal.io/products/pivotal-tcserver). These instructions require **tc Server 2.5** or later.
+1. If you do not already have tc Server, download and install the product from the [VMware tc Server download page](https://my.vmware.com/web/vmware/info/slug/application_platform/vmware_vfabric_tc_server/2_9) or the [Pivotal tc Server download page](https://network.pivotal.io/products/pivotal-tcserver). These instructions require **tc Server 2.9** or later.
2. The HTTP Session Management Module for tc Server is included in the Apache Geode installation package. After you install Apache Geode, you will find the module in the `tools/Modules` directory of the installation.
3. Unzip the module into the Pivotal tc Server `$CATALINA_HOME/templates` directory so that it creates `geode-p2p` and `geode-cs` subdirectories within the tc Server `templates` directory.
[26/50] [abbrv] incubator-geode git commit: Add new authentication
example. [#128343507]
Posted by rv...@apache.org.
Add new authentication example. [#128343507]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/06b71c9a
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/06b71c9a
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/06b71c9a
Branch: refs/staging/docs-grant1
Commit: 06b71c9ab0601b5190773b0c504154d52ace8aed
Parents: f778e4a
Author: Karen Miller <km...@pivotal.io>
Authored: Thu Sep 8 17:14:13 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Thu Sep 8 17:14:13 2016 -0700
----------------------------------------------------------------------
.../authentication_examples.html.md.erb | 169 ++++++-------------
.../authentication_overview.html.md.erb | 5 +-
.../security/authorization_example.html.md.erb | 2 +-
3 files changed, 54 insertions(+), 122 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/06b71c9a/managing/security/authentication_examples.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/authentication_examples.html.md.erb b/managing/security/authentication_examples.html.md.erb
index 9c75e61..6e0d050 100644
--- a/managing/security/authentication_examples.html.md.erb
+++ b/managing/security/authentication_examples.html.md.erb
@@ -1,122 +1,53 @@
---
-title: Authentication Examples
+title: Authentication Example
---
-This topic discusses the concepts and configurations for sample LDAP and PKCS implementations. Descriptions of their interfaces, classes and methods are available in the online API documentation.
-
-The security implementation of every installation is unique, so these examples cannot be used as is. These examples intend to provide a starting point. Modify them to handle the implementation-specific needs of your system.
-
-## <a id="authentication_examples__section_33A13D8566284AB999B5263844F61133" class="no-quick-link"></a>Using an LDAP Server for Client and Peer Authentication
-
-The LDAP sample code is within the Geode source tree in the `geode-core/src/test/java/com/gemstone/gemfire/security/templates/` directory. The implementation is in files `UserPasswordAuthInit.java`, `LdapUserAuthenticator.java`, and `UsernamePrincipal.java`.
-
-In the example, a client or joining peer submits its credentials to a server or locator, which in turn submits the credentials to the LDAP server. To be authenticated, the credentials must match one of the valid entries in the LDAP server. If the submitted credentials result in a connection to the LDAP server, then the connection is authenticated. If the connection to the LDAP server fails, an AuthenticationFailedException is sent back and the client or peer connection fails.
-
-These are the `gemfire.properties` file (or `gfsecurity.properties` file if you are creating a special restricted access file for security configuration) settings for client, and for all peers in the server system, including the servers and locators.
-
-- Client:
-
- ``` pre
- security-client-auth-init=com.gemstone.gemfire.security.templates.UserPasswordAuthInit.create
- security-username="username"
- security-password="password"
- ```
-
-- Server system members:
-
- ``` pre
- security-peer-auth-init=com.gemstone.gemfire.security.templates.UserPasswordAuthInit.create
- security-peer-authenticator=com.gemstone.gemfire.security.templates.LdapUserAuthenticator.create
- security-ldap-server="name of ldap server"
- security-ldap-basedn="ou=www, dc=xxx, dc=yyy, dc=zzz"
- ```
-
-LDAP authentication and authorization requires the LDAP server to have entries for each member that is authenticated by the system. The server also requires information to authorize or reject operations by authenticated clients when the authorization callback is invoked.
-
-During the client authentication process, a server searches for a specific entry in the LDAP server. The uid and password parameters submitted by the client are used to search the entries in the LDAP server. The LDAP authenticator is initialized with an LDAP base DN, which is the top level for the LDAP directory tree. The authenticator is also provided with the LDAP server name. The LDAP authenticator can be initialized to make a secure connection by setting the security-ldap-usessl property to true.
-
-The sample `LdapUserAuthenticator` class implements the `Authenticator` interface, which verifies the credentials provided in the properties as specified in member ID and returns the principal associated with the client. The `init` method for `LdapUserAuthenticator` gets the LDAP server name from the `security-ldap-server` property in the `gemfire.properties`. It also gets the LDAP server base DN name from the `security-ldap-basedn` property, and SSL usage information from the `security-ldap-usessl` property.
-
-## <a id="authentication_examples__section_6CF27B7574224218A4BA372EB6664732" class="no-quick-link"></a>Using PKCS for Encrypted Client Authentication
-
-The PKCS sample code is within the Geode source tree in the `geode-core/src/test/java/com/gemstone/gemfire/security/templates/` directory. The implementation is in files `PKCSAuthInit.java`, `PKCSAuthenticator.java`, and `PKCSPrincipal.java`.
-
-With this sample, clients send encrypted authentication credentials to a GemFire cache server when they attempt to connect to the server. The credentials are the alias name and digital signature created using the private key retrieved from the provided keystore. The server uses a corresponding public key to decrypt the credentials. If decryption is successful, the client is authenticated and it connects to the server. An unsuccessful decryption generates an `AuthenticationFailedException` that is sent to the client, and the client connection to the server is closed.
-
-These are the `gemfire.properties` file (or `gfsecurity.properties` file if you are creating a special restricted access file for security configuration) settings for client and server.
-
-- Client:
-
- ``` pre
- security-client-auth-init=com.gemstone.gemfire.security.templates.PKCSAuthInit.create
- security-keystorepath="keystore path"
- security-alias="alias"
- security-keystorepass="keystore password"
- ```
-
-- Server:
-
- ``` pre
- security-client-authenticator=com.gemstone.gemfire.security.templates.PKCSAuthenticator.create
- security-publickey-filepath="path and name of public key file"
- security-publickey-pass="password of public key file store on the server"
- ```
-
-The authenticator gets the path to the truststore from the `security-publickey-filepath` property in the `gemfire.properties` (or `gfsecurity.properties` file if you are creating a special restricted access file for security configuration).
-
-When the client requires authentication, `PKCSAuthInit` gets the alias retrieved from the `security-alias` property, and the keystore path from the `security-keystorepath` property. PKCSAuthInit also gets the password for the keystore file from the `security-keystorepass` property so the keystore can be opened.
-
-You can generate keys for encryption using the Java `keytool` utility, which is a key and certificate management utility located in the `jre/bin` directory of your Java JDK or JRE installation. The `keytool` utility manages a keystore, or database, of private keys and their associated X.509 certificate chains for authenticating the corresponding public keys. Certificates from trusted entities are also managed using `keytool`. See the Security Tools section at [http://download.oracle.com/javase/8/docs/technotes/tools](http://download.oracle.com/javase/8/docs/technotes/tools) for more information about using `keytool`. The public keys from the client keystores should be provided in the public keystore that is referenced by the `security-publickey-filepath` property.
-
-These are the steps to provide the keys, with example utility invocations:
-
-1. Generate a public and private key pair for the client:
-
- ``` pre
- keytool -genkeypair \
- -dname "cn=Your Name, ou=GemFire, o=GemStone, c=US" \
- -storetype PKCS12 \
- -keyalg RSA \
- -keysize 2048 \
- -alias gemfire \
- -keystore gemfire.keystore \
- -storepass your_password
- -validity 180
- ```
-
- This step creates a keystore called `gemfire.keystore` in the local directory and adds a public/private key pair to it.
-
-2. Export the self-signed certificate:
-
- ``` pre
- keytool -exportcert \
- -storetype PKCS12 \
- -keyalg RSA
- -keysize 2048
- -alias gemfire \
- -keystore gemfire.keystore \
- -storepass your_password
- -rfc \
- -file gemfire.cer
- ```
-
- After successfully exporting the certificate, you should see the following message:
-
- ``` pre
- Certificate stored in file <gemfire.cer>
- ```
-
- The above commands exports the certificate file to the current local directory.
-
-3. Import the signed certificate to the truststore:
-
- ``` pre
- keytool -importcert \
- -alias gemfire \
- -file gemfire.cer \
- -keystore certificatetruststore
- ```
-
- You will be prompted to enter your keystore password. After you have authenticated, the certificate appears. After you respond to the prompt "Trust this certificate?", the certificate is imported into the certificatetruststore keystore, creating it if necessary.
-
-Multiple certificates can be imported to the same truststore. The alias name used to generate the key pair and the alias name used to import the certificate to the truststore can be different, but the PKCS sample implementation assumes that both are the same. The credentials authenticator reads the truststore file and loads all the public keys from the truststore, along with the alias names.
+This example demonstrates the basics of an implementation of the
+`SecurityManager.authenticate` method.
+The remainder of the example may be found within the Apache Geode
+source code within the
+`geode-core/src/main/java/org/apache/geode/security/templates` directory.
+
+Of course, the security implementation of every installation is unique,
+so this example cannot be used in a production environment.
+Its use of the user name as a returned principal upon successful
+authentication is a particularly poor design choice,
+as any attacker that discovers the implementation can potentially
+spoof the system.
+
+This example assumes that a set of user name and password pairs
+representing users that may be successfully authenticated
+has been read into a data structure upon intialization.
+Any component that presents the correct password for a user name
+successfully authenticates,
+and its identity is verified as that user.
+Therefore, the implementation of the `authenticate` method
+checks that the user name provided within the `credentials` parameter
+ is in its data structure.
+If the user name is present,
+then the password provided within the `credentials` parameter
+is compared to the data structure's known password for that user name.
+Upon a match, the authentication is successful.
+
+``` pre
+public Object authenticate(final Properties credentials)
+ throws AuthenticationFailedException {
+ String user = credentials.getProperty(ResourceConstants.USER_NAME);
+ String password = credentials.getProperty(ResourceConstants.PASSWORD);
+
+ User userObj = this.userNameToUser.get(user);
+ if (userObj == null) {
+ throw new AuthenticationFailedException(
+ "SampleSecurityManager: wrong username/password");
+ }
+
+ if (user != null
+ && !userObj.password.equals(password)
+ && !"".equals(user)) {
+ throw new AuthenticationFailedException(
+ "SampleSecurityManager: wrong username/password");
+ }
+
+ return user;
+}
+```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/06b71c9a/managing/security/authentication_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/authentication_overview.html.md.erb b/managing/security/authentication_overview.html.md.erb
index ad3af66..fe38e10 100644
--- a/managing/security/authentication_overview.html.md.erb
+++ b/managing/security/authentication_overview.html.md.erb
@@ -18,8 +18,9 @@ system such as peers, clients, and those connecting to a JMX manager.
For secure transmission of sensitive information, like passwords, you can encrypt credentials using the Diffie-Hellman key exchange algorithm.
-- **[Authentication Examples](../../managing/security/authentication_examples.html)**
+- **[Authentication Example](../../managing/security/authentication_examples.html)**
- This topic discusses the concepts and configurations for sample LDAP and PKCS implementations. Descriptions of their interfaces, classes and methods are available in the online API documentation.
+ The example demonstrates the basics of an implementation of the
+`SecurityManager.authenticate` method.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/06b71c9a/managing/security/authorization_example.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/authorization_example.html.md.erb b/managing/security/authorization_example.html.md.erb
index faf2bf4..9d03f65 100644
--- a/managing/security/authorization_example.html.md.erb
+++ b/managing/security/authorization_example.html.md.erb
@@ -10,7 +10,7 @@ source code within the
Of course, the security implementation of every installation is unique,
so this example cannot be used in a production environment,
-as the roles and permissions will not match the neeeds of any
+as the roles and permissions will not match the needs of any
real distributed system.
This example assumes that a set of users, a set of roles
[34/50] [abbrv] incubator-geode git commit: Incomplete update of
setting credentials for authentication. [#130304427]
Posted by rv...@apache.org.
Incomplete update of setting credentials for authentication.
[#130304427]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/b9e16c0d
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/b9e16c0d
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/b9e16c0d
Branch: refs/staging/docs-grant1
Commit: b9e16c0dff53236654806877aee5e1bfb1518088
Parents: b40485b
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Sep 14 16:34:40 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Sep 14 16:34:40 2016 -0700
----------------------------------------------------------------------
.../implementing_authentication.html.md.erb | 87 +++++++++++++++++++-
managing/security/security-audit.html.md.erb | 2 +-
2 files changed, 85 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/b9e16c0d/managing/security/implementing_authentication.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_authentication.html.md.erb b/managing/security/implementing_authentication.html.md.erb
index c238be9..98b5505 100644
--- a/managing/security/implementing_authentication.html.md.erb
+++ b/managing/security/implementing_authentication.html.md.erb
@@ -10,15 +10,96 @@ All components use the same authentication mechanism.
When a component initiates a connection to the distributed system,
the `SecurityManager.authenticate` method is invoked.
-The component provides credentials in the form of `Properties`,
-which are passed to the `authenticate` method.
+The component provides its credentials in the form of properties
+as a parameter to the `authenticate` method.
+The credential is presumed to be the two properties:
+`security-username` and `security-password`.
The `authenticate` method is expected to either return an object
representing a principal or throw an `AuthenticationFailedException`.
+A well-designed `authenticate` method will have or will have a way of
+obtaining a set of known user and password pairs that can be compared
+to the credential presented.
+
+## How a Server Sets Its Credential
+
+In order to connect with a locator that does authentication,
+a server will need to set its credential, composed of the two properties
+`security-username` and `security-password`.
+There are two ways of accomplishing this:
+
+- Set the `security-username` and `security-password` in the server's
+`gfsecurity.properties` file that will be read upon server start up,
+as in the example
+
+ ``` pre
+ security-username=admin
+ security-password=xyz1234
+ ```
+The user name and password are stored in the clear, so the
+`gfsecurity.properties` file must be protected by restricting access with
+file system permissions.
+
+- Implement the `getCredentials` method of the `AuthInitialize` interface
+for the server.
+This callback's location is defined in the property `security-peer-auth-init`,
+as in the example
+
+ ``` pre
+ security-peer-auth-init=com.example.security.MyAuthInitialize
+ ```
+The implementation of `getCredentials` may then acquire values for
+the properties `security-username` and `security-password` in whatever way
+it wishes.
+It might look up values in a database or another external resource.
+
+## How a Cache Client Sets Its Credential
+
+In order to connect with a locator or a server that does authentication,
+a client will need to set its credential, composed of the two properties
+`security-username` and `security-password`.
+There are two ways of accomplishing this:
+
+- Set the `security-username` and `security-password` in the client's
+`gfsecurity.properties` file that will be read upon client start up,
+as in the example
+
+ ``` pre
+ security-username=webclient
+ security-password=xyz1234
+ ```
+The user name and password are stored in the clear, so the
+`gfsecurity.properties` file must be protected by restricting access with
+file system permissions.
+
+- Implement the `getCredentials` method of the `AuthInitialize` interface
+for the client.
+This callback's location is defined in the property `security-client-auth-init`,
+as in the example
+
+ ``` pre
+ security-client-auth-init=com.example.security.ClientAuthInitialize
+ ```
+The implementation of `getCredentials` may then acquire values for
+the properties `security-username` and `security-password` in whatever way
+it wishes.
+It might look up values in a database or another external resource,
+or it might prompt for values.
+
+## How Other Components Set Their Credentials
+
+gfsh prompts upon `gfsh connect`.
+
+Pulse prompts upon start up.
+
+Components connecting via the REST API do something.
+
+
## Implement SecurityManager Interface
-Complete these items to implement authentication.
+Complete these items to implement authentication done by either a
+locator or a server.
- Decide upon an authentication algorithm.
The [Authentication Example](authentication_examples.html)
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/b9e16c0d/managing/security/security-audit.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/security-audit.html.md.erb b/managing/security/security-audit.html.md.erb
index cec5e31..f35a29a 100644
--- a/managing/security/security-audit.html.md.erb
+++ b/managing/security/security-audit.html.md.erb
@@ -24,7 +24,7 @@ These configuration files should be readable and writeable *only* by the dedicat
- `gemfire.properties`
- `cache.xml`
- `gfsecurity.properties`
- **Note:** A default `gfsecurity.properties` is not provided in the `defaultConfigs` directory. If you choose to use this properties file, you must create it manually. See [Where to Place Security Settings](implementing_security.html) for more information.
+ A default `gfsecurity.properties` is not provided in the `defaultConfigs` directory. If you choose to use this properties file, you must create it manually. A clear text user name and associated clear text password may be in this file for authentication purposes. The file system's access rights are relied upon to protect this sensitive information.
The default location of the `gemfire.properties` and `cache.xml` configuration files is the `defaultConfigs` child directory of the main installation directory.
[09/50] [abbrv] incubator-geode git commit: Fixed a positioning issue
in a link.
Posted by rv...@apache.org.
Fixed a positioning issue in a link.
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/8a568474
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/8a568474
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/8a568474
Branch: refs/staging/docs-grant1
Commit: 8a568474efd4681e421ee12e864189fed66abf8a
Parents: 705677d
Author: Dave Barnes <db...@pivotal.io>
Authored: Thu Sep 1 11:40:20 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Thu Sep 1 11:40:20 2016 -0700
----------------------------------------------------------------------
managing/security/security_audit_overview.html.md.erb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/8a568474/managing/security/security_audit_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/security_audit_overview.html.md.erb b/managing/security/security_audit_overview.html.md.erb
index 402fe69..307dc2c 100644
--- a/managing/security/security_audit_overview.html.md.erb
+++ b/managing/security/security_audit_overview.html.md.erb
@@ -6,7 +6,7 @@ title: Security Detail Considerations
This section gathers discrete details in one convenient location to better help you assess and configure the security of your environment.
-- **[External Interfaces, Ports, and Services](security-audit.html#topic_686158E9AFBD47518BE1B4BEB232C190)**
+- **[External Interfaces, Ports, and Services](security-audit.html)**
Geode processes use either UDP or TCP/IP ports to communicate with other processes or clients.
[06/50] [abbrv] incubator-geode git commit: Merge remote-tracking
branch 'origin/develop' into feature/IntegratedSecurity
Posted by rv...@apache.org.
Merge remote-tracking branch 'origin/develop' into feature/IntegratedSecurity
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/623b6182
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/623b6182
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/623b6182
Branch: refs/staging/docs-grant1
Commit: 623b6182b9d3f0fd6217a1f0e807e6554e2b7244
Parents: 10f9d9a 62a3bf9
Author: Karen Miller <km...@pivotal.io>
Authored: Thu Sep 1 08:49:39 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Thu Sep 1 08:49:39 2016 -0700
----------------------------------------------------------------------
images/DataManagement-9.gif | Bin 7295 -> 0 bytes
images/DataManagement-9.png | Bin 0 -> 48188 bytes
managing/heap_use/heap_management.html.md.erb | 2 +-
.../client-cache-elements-list.html.md.erb | 26 +++++++++----------
reference/topics/client-cache.html.md.erb | 11 ++++----
5 files changed, 19 insertions(+), 20 deletions(-)
----------------------------------------------------------------------
[13/50] [abbrv] incubator-geode git commit: Write Implementing
Authorization section [#129183251]
Posted by rv...@apache.org.
Write Implementing Authorization section [#129183251]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/37d050cf
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/37d050cf
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/37d050cf
Branch: refs/staging/docs-grant1
Commit: 37d050cfd2ece51472d35a9f55686e864529f3cd
Parents: 7c8acc5
Author: Karen Miller <km...@pivotal.io>
Authored: Tue Sep 6 13:53:26 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Tue Sep 6 13:53:26 2016 -0700
----------------------------------------------------------------------
.../implementing_authorization.html.md.erb | 244 ++++++++++++++++++-
1 file changed, 233 insertions(+), 11 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/37d050cf/managing/security/implementing_authorization.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_authorization.html.md.erb b/managing/security/implementing_authorization.html.md.erb
index cf89f24..87b4135 100644
--- a/managing/security/implementing_authorization.html.md.erb
+++ b/managing/security/implementing_authorization.html.md.erb
@@ -4,23 +4,245 @@ title: Implementing Authorization
## How Authorization Works
-The security framework establishes trust between members during authentication. In a client/server system, you can use this trust to grant or withhold a client's cache access and modification requests.
+When a component requests an operation,
+the `SecurityManager.authorize` method is invoked.
+It is passed the principal of the operation's requester
+and a `ResourcePermission`, which describes the operation requested.
-Access rights can be checked before the client operation is performed and before results of the operation are sent back to the client. Access control is done according to your configurations and programmatic plug-ins.
+The implementation of the `SecurityManager.authorize` method
+makes a decision as to whether or not the principal will be granted permission
+to carry out the operation.
+It returns a boolean in which a return value of `true` permits
+the operation,
+and a return value of `false` prevents the operation.
-<img src="../../images/security-4.gif" id="how_authorization_works__image_254428E85E8B47F9B558DA4C5DC02B93" class="image" />
-The principal, which you associate with the client when it is authenticated, is used by the authorization plug-in to allow or disallow each operation. Geode security invokes this callback with the principal and the requested operation, and permits or bars the operation depending on the result of the callback. The callback also has access to the operation data, such as the key and value for a `put`, which you can use to determine authorization. In addition, you can program the callback to change some of the operation data, such as the value for a `put` or the operation result.
+A well-designed `authorize` method will have or will have a way of obtaining
+a mapping of principals to the operations (in the form of resource permissions)
+that they are permitted to do.
-All client operations sent to the server can be authorized. The operations checked by the server are listed in `com.gemstone.gemfire.cache.operations.OperationContext.OperationCode`.
+## Resource Permissions
-**Note:**
-`Region` query shortcut methods are all sent to the server as `query` operations.
+All operations are described by an instance of the `ResourcePermission` class.
+A permission contains the `Resource` data member,
+which classifies whether the operation as working on
-All client operations that return a result (like `get` and `query`) and all notifications can also be authorized in the post-operation phase where the callback can peek and even modify the result being sent out.
+- cache data; value is `DATA`
+- the distributed system; value is `CLUSTER`
-## Resource Permissions
+A permission also contains the `Operation` data member,
+which classifies whether the operation as
+
+- reading; value is `READ`
+- changing information; value is `WRITE`
+- making administrative changes; value is `MANAGE`
+
+The operations are not hierarchical;
+`MANAGE` does not imply `WRITE`, and `WRITE` does not imply `READ`.
+
+Some operations further specify a region name in the permission.
+This permits restricting operations on that region to only those
+authorized principals.
+And within a region, some operations may specify a key.
+This permits restricting operations on that key within that region to
+only those authorized principals.
+
+This table classifies the permissions assigned for operations common to
+a Client-Server interaction.
+
+| Client Operation | Assigned `ResourcePermission`
+|------------------------------------|-------------------------------------|
+| get function attribute | CLUSTER:READ |
+| create region | DATA:MANAGE |
+| destroy region | DATA:MANAGE |
+| Region.Keyset | DATA:READ:RegionName |
+| Region.query | DATA:READ:RegionName |
+| Region.getAll | DATA:READ:RegionName |
+| Region.getAll with a list of keys | DATA:READ:RegionName:Key |
+| Region.getEntry | DATA:READ:RegionName |
+| Region.containsKeyOnServer(key) | DATA:READ:RegionName:Key |
+| Region.get(key) | DATA:READ:RegionName:Key |
+| Region.registerInterest(key) | DATA:READ:RegionName:Key |
+| Region.registerInterest(regex) | DATA:READ:RegionName |
+| Region.unregisterInterest(key) | DATA:READ:RegionName:Key |
+| Region.unregisterInterest(regex) | DATA:READ:RegionName |
+| execute function | DATA:WRITE |
+| clear region | DATA:WRITE:RegionName |
+| Region.putAll | DATA:WRITE:RegionName |
+| Region.clear | DATA:WRITE:RegionName |
+| Region.removeAll | DATA:WRITE:RegionName |
+| Region.destroy(key) | DATA:WRITE:RegionName:Key |
+| Region.invalidate(key) | DATA:WRITE:RegionName:Key |
+| invalidate key (DIFFERENT?) | DATA:WRITE:RegionName:Key |
+| Region.destroy(key) | DATA:WRITE:RegionName:Key |
+| destroy key (DIFFERENT?) | DATA:WRITE:RegionName:Key |
+| Region.put(key) | DATA:WRITE:RegionName:Key |
+| Region.replace | DATA:WRITE:RegionName:Key |
+
+
+This table classifies the permissions assigned for `gfsh` operations.
+
+| `gfsh` Command | Assigned `ResourcePermission`
+|----------------------------------------|----------------------------------|
+| alter disk-store | DATA:MANAGE |
+| alter region | DATA:MANAGE:RegionName |
+| alter runtime | CLUSTER:MANAGE |
+| backup disk-store | DATA:READ |
+| change loglevel | CLUSTER:WRITE |
+| clear defined indexes | DATA:MANAGE |
+| close durable-client | DATA:MANAGE |
+| close durable-cq | DATA:MANAGE |
+| compact disk-store | DATA:MANAGE |
+| compact offline-disk-store | DATA:MANAGE |
+| configure pdx | DATA:MANAGE |
+| create async-event-queue | DATA:MANAGE |
+| create defined indexes | DATA:MANAGE |
+| create disk-store | DATA:MANAGE |
+| create gateway-receiver | DATA:MANAGE |
+| create gateway-sender | DATA:MANAGE |
+| create index | DATA:MANAGE:RegionName |
+| create region | DATA:MANAGE |
+| define index | DATA:MANAGE:RegionName |
+| deploy | DATA:MANAGE |
+| describe client | CLUSTER:READ |
+| describe config | CLUSTER:READ |
+| describe disk-store | CLUSTER:READ |
+| describe member | CLUSTER:READ |
+| describe offline-disk-store | CLUSTER:READ |
+| describe region | CLUSTER:READ |
+| destroy disk-store | DATA:MANAGE |
+| destroy function | DATA:MANAGE |
+| destroy index | DATA:MANAGE or DATA:MANAGE:RegionName |
+| destroy region | DATA:MANAGE |
+| disconnect | DATA:MANAGE |
+| echo | DATA:MANAGE |
+| encrypt password | DATA:MANAGE |
+| execute function | DATA:MANAGE |
+| export cluster-configuration | CLUSTER:READ |
+| export config | CLUSTER:READ |
+| export data | CLUSTER:READ |
+| export logs | CLUSTER:READ |
+| export offline-disk-store | CLUSTER:READ |
+| export stack-traces | CLUSTER:READ |
+| gc | CLUSTER:MANAGE |
+| get --key=key1 --region=region1 | DATA:READ:RegionName:Key |
+| import data | DATA:WRITE:RegionName |
+| import cluster-configuration | DATA:MANAGE |
+| list async-event-queues | CLUSTER:READ |
+| list clients | CLUSTER:READ |
+| list deployed | CLUSTER:READ |
+| list disk-stores | CLUSTER:READ |
+| list durable-cqs | CLUSTER:READ |
+| list functions | CLUSTER:READ |
+| list gateways | CLUSTER:READ |
+| list indexes | CLUSTER:READ |
+| list members | CLUSTER:READ |
+| list regions | DATA:READ |
+| load-balance gateway-sender | DATA:MANAGE |
+| locate entry | DATA:READ:RegionName:Key |
+| netstat | CLUSTER:READ |
+| pause gateway-sender | DATA:MANAGE |
+| pdx rename | DATA:MANAGE |
+| put --key=key1 --region=region1 | DATA:WRITE:RegionName:Key |
+| query | DATA:READ:RegionName |
+| rebalance | DATA:MANAGE |
+| remove | DATA:WRITE:RegionName or DATA:WRITE:RegionName:Key |
+| resume gateway-sender | DATA:MANAGE |
+| revoke mising-disk-store | DATA:MANAGE |
+| show dead-locks | CLUSTER:READ |
+| show log | CLUSTER:READ |
+| show metrics | CLUSTER:READ |
+| show missing-disk-stores | CLUSTER:READ |
+| show subscription-queue-size | CLUSTER:READ |
+| shutdown | CLUSTER:MANAGE |
+| start gateway-receiver | DATA:MANAGE |
+| start gateway-sender | DATA:MANAGE |
+| start server | CLUSTER:MANAGE |
+| status cluster-config-service | CLUSTER:READ |
+| status gateway-receiver | CLUSTER:READ |
+| status gateway-sender | CLUSTER:READ |
+| status locator | CLUSTER:READ |
+| status server | CLUSTER:READ |
+| stop gateway-receiver | DATA:MANAGE |
+| stop gateway-receiver | DATA:MANAGE |
+| stop locator | CLUSTER:MANAGE |
+| stop server | CLUSTER:MANAGE |
+| undeploy | DATA:MANAGE |
+
+The `gfsh connect` does not have a permission,
+as it is the operation that invokes authentication.
+These `gfsh` commands do not have permission defined,
+as they do not interact with the distributed system.
+
+- `gfsh describe connection`, which describes the `gfsh` end of the connection
+- `gfsh debug`, which toggles the mode within `gfsh`
+- `gfsh exit`
+- `gfsh help`
+- `gfsh hint`
+- `gfsh history`
+- `gfsh run`, although individual commands within the script
+will go through authorization
+- `gfsh set variable`
+- `gfsh sh`
+- `gfsh sleep`
+- `validate offline-disk-store`
+- `gfsh version`
+
+This table classifies the permissions assigned for JMX operations.
+
+| JMX Operation | Assigned `ResourcePermission`
+|----------------------------------------------|-----------------------------|
+| DistributedSystemMXBean.shutdownAllMembers | CLUSTER:MANAGE |
+| ManagerMXBean.start | CLUSTER:MANAGE |
+| ManagerMXBean.stop | CLUSTER:MANAGE |
+| ManagerMXBean.createManager | CLUSTER:MANAGE |
+| ManagerMXBean.shutDownMember | CLUSTER:MANAGE |
+| Mbeans get attributes | CLUSTER:READ |
+| MemberMXBean.showLog | CLUSTER:READ |
+| DistributedSystemMXBean.changerAlertLevel | CLUSTER:WRITE |
+| ManagerMXBean.setPulseURL | CLUSTER:WRITE |
+| ManagerMXBean.setStatusMessage | CLUSTER:WRITE |
+| CacheServerMXBean.closeAllContinuousQuery | DATA:MANAGE |
+| CacheServerMXBean.closeContinuousQuery | DATA:MANAGE |
+| CacheServerMXBean.executeContinuousQuery | DATA:READ |
+| DiskStoreMXBean.flush | DATA:MANAGE |
+| DiskStoreMXBean.forceCompaction | DATA:MANAGE |
+| DiskStoreMXBean.forceRoll | DATA:MANAGE |
+| DiskStoreMXBean.setDiskUsageCriticalPercentage | DATA:MANAGE |
+| DiskStoreMXBean.setDiskUsageWarningPercentage | DATA:MANAGE |
+| DistributedSystemMXBean.revokeMissingDiskStores| DATA:MANAGE |
+| DistributedSystemMXBean.setQueryCollectionsDepth| DATA:MANAGE |
+| DistributedSystemMXBean.setQueryResultSetLimit | DATA:MANAGE |
+| DistributedSystemMXBean.backupAllMembers | DATA:READ |
+| DistributedSystemMXBean.queryData | DATA:READ |
+| DistributedSystemMXBean.queryDataForCompressedResult | DATA:READ |
+| GatewayReceiverMXBean.pause | DATA:MANAGE |
+| GatewayReceiverMXBean.rebalance | DATA:MANAGE |
+| GatewayReceiverMXBean.resume | DATA:MANAGE |
+| GatewayReceiverMXBean.start | DATA:MANAGE |
+| GatewayReceiverMXBean.stop | DATA:MANAGE |
+| GatewaySenderMXBean.pause | DATA:MANAGE |
+| GatewaySenderMXBean.rebalance | DATA:MANAGE |
+| GatewaySenderMXBean.resume | DATA:MANAGE |
+| GatewaySenderMXBean.start | DATA:MANAGE |
+| GatewaySenderMXBean.stop | DATA:MANAGE |
+| LockServiceMXBean.becomeLockGrantor | DATA:MANAGE |
+| MemberMXBean.compactAllDiskStores | DATA:MANAGE |
+
+## Implement Authorization
-## Implement SecurityManager Interface
+Complete these items to implement authorization.
-## Post Processing Callbacks
+- Decide upon an authorization algorithm.
+The [Authorization Example](authorization_example.html)
+stores a mapping of which principals (users) are permitted to do
+which operations.
+The algorithm bases its decision
+on a look up of the permissions granted to the principal attempting
+the operation.
+- Define the `security-manager` and `security-enabled-components` properties.
+See [Enable Security with Property Definitions](enable_security.html)
+for details about these properties.
+- Implement the `authorize` method of the `SecurityManager` interface.
+- Define any extra resources that the implemented authorization algorithm
+needs in order to make a decision.
[19/50] [abbrv] incubator-geode git commit: Detail the authorization
example [#128343939]
Posted by rv...@apache.org.
Detail the authorization example [#128343939]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/f6d9c2b9
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/f6d9c2b9
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/f6d9c2b9
Branch: refs/staging/docs-grant1
Commit: f6d9c2b9c01039c9bdfce717f11acc8498128f78
Parents: b37c19f
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Sep 7 12:36:19 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Sep 7 12:36:19 2016 -0700
----------------------------------------------------------------------
.../security/authorization_example.html.md.erb | 137 +++++++------------
1 file changed, 46 insertions(+), 91 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/f6d9c2b9/managing/security/authorization_example.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/authorization_example.html.md.erb b/managing/security/authorization_example.html.md.erb
index e474f9e..faf2bf4 100644
--- a/managing/security/authorization_example.html.md.erb
+++ b/managing/security/authorization_example.html.md.erb
@@ -2,97 +2,52 @@
title: Authorization Example
---
-This topic discusses the authorization example provided in the product under `templates/security` using `XmlAuthorization.java`, `XmlErrorHandler.java`, and `authz6_0.dtd`.
-
-The security implementation of every installation is unique, so this example cannot be used as is. This example intends to provide a starting point. Modify it to handle the implementation-specific needs of your system.
-
-`XmlAuthorization` provides authorization for each region at the operation level by using the permissions specified in an XML file. The sample implementation also shows the post-authorization implementation for the function execution operation. For pre-operation, all the required values are available.
-
-You can configure authorization for all server region operations on a per-region and per-operation basis by using a role-based mechanism. A role can be provided with permissions to execute operations for each region. Each principal name can be associated with a set of roles.
-
-Information such as the region reference, arguments, the operation being invoked, and a reference to the cache instance can be made available to the `XmlAuthorization` callback. If an authenticated client is not authorized to perform an operation, the operation fails with a `NotAuthorizedException`.
-
-## <a id="authorization_example__section_076277507223430E9455E3DE5150D656" class="no-quick-link"></a>Server Settings
-
-These are the `gemfire.properties` file (or `gfsecurity.properties` file if you are creating a special restricted access file for security configuration) settings for each server:
-
-``` pre
-security-client-accessor=templates.security.XmlAuthorization.create
-security-authz-xml-uri=<URI of XML file>
-```
-
-## <a id="authorization_example__section_85F79DD53FD7453D87DF915A91595218" class="no-quick-link"></a>XML File Sample Settings
-
-The `XmlAuthorization` sample is configured through an XML file, which is described in the `authz6_0.dtd` in the security templates directory. See the dtd for documentation about the elements and attributes you use to configure `XmlAuthorization`. To run the example, create an XML file following the dtd specifications.
-
-The user names you use should be the strings returned by the `Principal.getName` method of the `Authenticator` configured on the server
-
-This topic lists an example XML file for the dtd. The example defines five roles:
-1. `reader`
-2. `writer`
-3. `cacheOps`
-4. `queryRegions`
-5. `onRegionFunctionExecutor`
-
-The listing below is a sample XML file:
-
-- The permissions for each of the roles are described in the permission tags.
-- The `reader`, `writer`, and `cacheOps` roles have no regions mentioned, so they apply to all regions.
-- The `queryRegions` role has permissions on `Portfolios` and `Positions` regions.
-- The role of `onRegionFunctionExecutor` can only operate on regions `secureRegion` and `Positions`, and only with functions with ids `SecureFunction` or `OptimizationFunction`. On the functions, `optimizeForWrite` must be `false` and `keySet` must be `KEY-0` and `KEY-1`.
+This example demonstrates the basics of an implementation of the
+`SecurityManager.authorize` method.
+The remainder of the example may be found within the Apache Geode
+source code within the
+`geode-core/src/main/java/org/apache/geode/security/templates` directory.
+
+Of course, the security implementation of every installation is unique,
+so this example cannot be used in a production environment,
+as the roles and permissions will not match the neeeds of any
+real distributed system.
+
+This example assumes that a set of users, a set of roles
+that a user might take on within the system,
+and a mapping of users to their roles are described
+in a JSON format file.
+The roles define a set of authorized resource permissions granted
+for users in those roles.
+Code not shown here parses the file to compose a data structure
+with the information on roles and users.
+The `authorize` callback denies permission for any operation
+that does not have a principal representing the identity of the
+operation's requester.
+Given the principal,
+the method iterates through the data structure searching for the
+necessary permissions for the principal.
+When the necessary permission is found,
+authorization is granted by returning the value `true`.
+If the permission is not found in the data structure,
+then the method returns `false`, denying authorization of the operation.
``` pre
-<!DOCTYPE acl PUBLIC
-"-//Example Systems, Inc.//Example XML Authorization 1.0//EN"
-"http://www.example.com/dtd/authz6_0.dtd">
-
-<acl>
-<role name="reader">
- <user>reader</user>
- <user>admin</user>
-</role>
-<role name="writer">
- <user>writer</user>
- <user>admin</user>
-</role>
-<role name="cacheOps">
- <user>admin</user>
-</role>
-<role name="queryRegions">
- <user>query</user>
-</role>
-<role name="onRegionFunctionExecutor">
- <user>admin</user>
-</role>
-<permission role="cacheOps">
- <operation>QUERY</operation>
- <operation>EXECUTE_CQ</operation>
- <operation>STOP_CQ</operation>
- <operation>CLOSE_CQ</operation>
- <operation>REGION_CREATE</operation>
- <operation>REGION_DESTROY</operation>
-</permission>
-<permission role="reader">
- <operation>GET</operation>
- <operation>REGISTER_INTEREST</operation>
- <operation>UNREGISTER_INTEREST</operation>
- <operation>KEY_SET</operation>
- <operation>CONTAINS_KEY</operation>
-</permission>
-<permission role="writer">
- <operation>PUT</operation>
- <operation>DESTROY</operation>
- <operation>REGION_CLEAR</operation>
-</permission>
-<permission role="queryRegions" regions="/Portfolios,Positions">
- <operation>QUERY</operation>
- <operation>EXECUTE_CQ</operation>
- <operation>STOP_CQ</operation>
- <operation>CLOSE_CQ</operation>
-</permission>
-<permission role="onRegionFunctionExecutor" regions="secureRegion,Positions">
- <operation functionIds="SecureFunction,OptimizationFunction"
- optimizeForWrite="false" keySet="KEY-0,KEY-1">EXECUTE_FUNCTION</operation>
-</permission>
-</acl>
+public boolean authorize(final Object principal, final ResourcePermission context) {
+ if (principal == null) return false;
+
+ User user = this.userNameToUser.get(principal.toString());
+ if (user == null) return false; // this user is not authorized to do anything
+
+ // check if the user has this permission defined in the context
+ for (Role role : this.userNameToUser.get(user.name).roles) {
+ for (Permission permitted : role.permissions) {
+ if (permitted.implies(context)) {
+ return true;
+ }
+ }
+ }
+
+ return false;
+}
```
[47/50] [abbrv] incubator-geode git commit: Incorporate OQL
aggregates documentation. [#130418485] [#130956491]
Posted by rv...@apache.org.
Incorporate OQL aggregates documentation. [#130418485] [#130956491]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/21cdeffa
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/21cdeffa
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/21cdeffa
Branch: refs/staging/docs-grant1
Commit: 21cdeffac9211d388f0e56f0f4cf1abef5dcfd54
Parents: ada7dcb
Author: Karen Miller <km...@pivotal.io>
Authored: Tue Sep 27 11:32:36 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Tue Sep 27 11:32:36 2016 -0700
----------------------------------------------------------------------
developing/query_select/aggregates.html.md.erb | 92 +++++++++++++++
.../the_select_statement.html.md.erb | 118 -------------------
...ictions_and_unsupported_features.html.md.erb | 13 --
3 files changed, 92 insertions(+), 131 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/21cdeffa/developing/query_select/aggregates.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/query_select/aggregates.html.md.erb b/developing/query_select/aggregates.html.md.erb
new file mode 100644
index 0000000..1a4e0aa
--- /dev/null
+++ b/developing/query_select/aggregates.html.md.erb
@@ -0,0 +1,92 @@
+---
+title: OQL Aggregate Functions
+---
+
+The aggregate functions
+```MIN```,
+```MAX```,
+```AVG```,
+```AVG``` over a DISTINCT expression,
+```SUM``` over a DISTINCT expression,
+```COUNT```, and
+```COUNT``` over a DISTINCT expression
+are supported.
+The ```GROUP BY``` extension is also supported where appropriate.
+
+The ```MIN``` function returns the smallest of the selected
+expression.
+The type of the expression must evaluate to a
+```java.lang.Comparable```.
+
+The ```MAX``` function returns the largest of the selected
+expression.
+The type of the expression must evaluate to a
+```java.lang.Comparable```.
+
+The ```AVG``` function returns the arithmetic mean of the set
+formed by the selected expression.
+The type of the expression must evaluate to a
+```java.lang.Number```.
+For partitioned regions,
+each node's buckets provide both a sum and the number of elements
+to the node executing the query,
+such that a correct average may be computed.
+
+The ```AVG``` function where the DISTINCT modifier is applied
+to the expression returns the arithmetic mean of the set
+of unique (distinct) values.
+The type of the expression must evaluate to a
+```java.lang.Number```.
+For partitioned regions,
+the distinct values in a node's buckets are returned
+to the node executing the query.
+The query node can then calculate the avarage over
+the values that are unique across nodes,
+after eliminating duplicate values that come from separate nodes.
+
+The ```SUM``` function returns the sum over the set
+formed by the selected expression.
+The type of the expression must evaluate to a
+```java.lang.Number```.
+For partitioned regions,
+each node's buckets compute a sum over that node,
+returning that sum
+to the node executing the query,
+when then sums across all nodes.
+
+The ```SUM``` function where the DISTINCT modifier is applied
+to the expression returns the sum over the set
+of unique (distinct) values.
+The type of the expression must evaluate to a
+```java.lang.Number```.
+For partitioned regions,
+the distinct values in a node's buckets are returned
+to the node executing the query.
+The query node can then calculate the sum over
+the values that are unique across nodes,
+after eliminating duplicate values that come from separate nodes.
+
+The ```COUNT``` function returns the quantity of values in the set
+formed by the selected expression.
+For example, to return the quantity of employees who have a
+positive sales amount:
+
+``` pre
+SELECT count(e.sales) FROM /employees e WHERE e.sales > 0.0
+```
+
+The ```COUNT``` function where the DISTINCT modifier is applied
+returns the quantity of unique (distinct) values in the set
+formed by the selected expression.
+
+## GROUP BY Extension for Aggregate Functions
+
+```GROUP BY``` is required
+when aggregate functions are used in combination
+with other selected items.
+It permits ordering.
+For example,
+
+``` pre
+SELECT ID, MAX(e.sales) FROM /employees e GROUP BY ID
+```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/21cdeffa/developing/query_select/the_select_statement.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/query_select/the_select_statement.html.md.erb b/developing/query_select/the_select_statement.html.md.erb
index 04f9f3b..04d14df 100644
--- a/developing/query_select/the_select_statement.html.md.erb
+++ b/developing/query_select/the_select_statement.html.md.erb
@@ -201,121 +201,3 @@ FROM /exampleRegion p, p.positions.values pos
WHERE p.ID > 0 OR p.status = 'active' OR pos.secId
OR pos.secId = 'IBM'
```
-
-<div style="background-color:lightyellow;">
-<h2>(Experimental Feature) Aggregate Functions</h2>
-
-<p>
-Some prose here about being experimental.
-</p>
-
-<p>
-The aggregate functions
-<code>MIN</code>,
-<code>MAX</code>,
-<code>AVG</code>,
-<code>AVG</code> over a DISTINCT expression,
-<code>SUM</code> over a DISTINCT expression,
-<code>COUNT</code>, and
-<code>COUNT</code> over a DISTINCT expression
-are supported.
-The <code>GROUP BY</code> extension is also supported where appropriate.
-</p>
-
-<p>
-The <code>MIN</code> function returns the smallest of the selected
-expression.
-The type of the expression must evaluate to a
-<code>java.lang.Comparable</code>.
-</p>
-
-<p>
-The <code>MAX</code> function returns the largest of the selected
-expression.
-The type of the expression must evaluate to a
-<code>java.lang.Comparable</code>.
-</p>
-
-<p>
-The <code>AVG</code> function returns the arithmetic mean of the set
-formed by the selected expression.
-The type of the expression must evaluate to a
-<code>java.lang.Number</code>.
-For partitioned regions,
-each node's buckets provide both a sum and the number of elements
-to the node executing the query,
-such that a correct average may be computed.
-</p>
-
-<p>
-The <code>AVG</code> function where the DISTINCT modifier is applied
-to the expression returns the arithmetic mean of the set
-of unique (distinct) values.
-The type of the expression must evaluate to a
-<code>java.lang.Number</code>.
-For partitioned regions,
-the distinct values in a node's buckets are returned
-to the node executing the query.
-The query node can then calculate the avarage over
-the values that are unique across nodes,
-after eliminating duplicate values that come from separate nodes.
-</p>
-
-<p>
-The <code>SUM</code> function returns the sum over the set
-formed by the selected expression.
-The type of the expression must evaluate to a
-<code>java.lang.Number</code>.
-For partitioned regions,
-each node's buckets compute a sum over that node,
-returning that sum
-to the node executing the query,
-when then sums across all nodes.
-</p>
-
-<p>
-The <code>SUM</code> function where the DISTINCT modifier is applied
-to the expression returns the sum over the set
-of unique (distinct) values.
-The type of the expression must evaluate to a
-<code>java.lang.Number</code>.
-For partitioned regions,
-the distinct values in a node's buckets are returned
-to the node executing the query.
-The query node can then calculate the sum over
-the values that are unique across nodes,
-after eliminating duplicate values that come from separate nodes.
-</p>
-
-<p>
-The <code>COUNT</code> function returns the quantity of values in the set
-formed by the selected expression.
-For example, to return the quantity of employees who have a
-positive sales amount:
-</p>
-<pre>
-SELECT count(e.sales) FROM /employees e WHERE e.sales > 0.0
-</pre>
-<p>
-The <code>COUNT</code> function where the DISTINCT modifier is applied
-returns the quantity of unique (distinct) values in the set
-formed by the selected expression.
-</p>
-</div>
-
-<div style="background-color:lightyellow;">
-<h2>(Experimental Feature) GROUP BY Extension for Aggregate Functions</h2>
-
-<p>
-<code>GROUP BY</code> is required
-when aggregate functions are used in combination
-with other selected items.
-It permits ordering.
-For example,
-</p>
-
-<pre>
-SELECT ID, MAX(e.sales) FROM /employees e GROUP BY ID
-</pre>
-
-</div>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/21cdeffa/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb b/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
index baac020..44a5e73 100644
--- a/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
+++ b/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
@@ -16,16 +16,3 @@ At a high level, Geode does not support the following querying features:
In addition, there are some specific limitations on partitioned region querying. See [Partitioned Region Query Restrictions](../query_additional/partitioned_region_query_restrictions.html#concept_5353476380D44CC1A7F586E5AE1CE7E8).
-<div style="background-color:lightyellow;">
-<h2> Features Supported on an Experimental Basis</h2>
-
-<p>
-These features are supported,
-but their experimental implementation may change:
-</p>
-
-<ul>
-<li> GROUP BY
-<li> The aggregate functions AVG, MIN, MAX, COUNT, SUM
-</ul>
-</div>
[07/50] [abbrv] incubator-geode git commit: Fix typo in
enable_security.html link.
Posted by rv...@apache.org.
Fix typo in enable_security.html link.
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/1ecc0ebb
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/1ecc0ebb
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/1ecc0ebb
Branch: refs/staging/docs-grant1
Commit: 1ecc0ebba4bb7fa5f1670007ed6c62c653648fc8
Parents: 623b618
Author: Karen Miller <km...@pivotal.io>
Authored: Thu Sep 1 08:57:07 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Thu Sep 1 08:57:07 2016 -0700
----------------------------------------------------------------------
managing/security/chapter_overview.html.md.erb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/1ecc0ebb/managing/security/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/chapter_overview.html.md.erb b/managing/security/chapter_overview.html.md.erb
index da66a96..9269bd6 100644
--- a/managing/security/chapter_overview.html.md.erb
+++ b/managing/security/chapter_overview.html.md.erb
@@ -17,7 +17,7 @@ features help to secure the distributed system.
Apache Geode can authenticate peer system members and clients. It can also authorize cache operations on a server from clients.
-- **[Enable Security with Property Definitions](../../managing/security/enable_security`.html)**
+- **[Enable Security with Property Definitions](../../managing/security/enable_security.html)**
- **[Authentication](../../managing/security/authentication_overview.html)**
[46/50] [abbrv] incubator-geode git commit: Remove JVSD docs from
user guide [#130994985]
Posted by rv...@apache.org.
Remove JVSD docs from user guide [#130994985]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/ada7dcb9
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/ada7dcb9
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/ada7dcb9
Branch: refs/staging/docs-grant1
Commit: ada7dcb9ce77cca48e12b4ab547bb4405a111b8a
Parents: d6dc0fe
Author: Dave Barnes <db...@pivotal.io>
Authored: Fri Sep 23 10:23:22 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Fri Sep 23 10:23:22 2016 -0700
----------------------------------------------------------------------
.../statistics/viewing_statistics.html.md.erb | 2 +-
tools_modules/book_intro.html.md.erb | 3 -
tools_modules/jvsd.html.md.erb | 111 -------------------
3 files changed, 1 insertion(+), 115 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ada7dcb9/managing/statistics/viewing_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/statistics/viewing_statistics.html.md.erb b/managing/statistics/viewing_statistics.html.md.erb
index 6c983aa..eba7f3a 100644
--- a/managing/statistics/viewing_statistics.html.md.erb
+++ b/managing/statistics/viewing_statistics.html.md.erb
@@ -2,6 +2,6 @@
title: Viewing Archived Statistics
---
-When sampling and archiving are enabled, you can examine archived historical data to help diagnose performance problems. Study statistics in archive files by using the gfsh `show metrics` command. You may also wish to use a separate statistics display utility, such as [Java Visual Statistics Display (JVSD)](../../tools_modules/jvsd.html).
+When sampling and archiving are enabled, you can examine archived historical data to help diagnose performance problems. Study statistics in archive files by using the gfsh `show metrics` command. You may also wish to use a separate statistics display utility.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ada7dcb9/tools_modules/book_intro.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/book_intro.html.md.erb b/tools_modules/book_intro.html.md.erb
index faa6527..962f551 100644
--- a/tools_modules/book_intro.html.md.erb
+++ b/tools_modules/book_intro.html.md.erb
@@ -30,8 +30,5 @@ title: Tools and Modules
The Geode Redis adapter allows Geode to function as a drop-in replacement for a Redis data store, letting Redis applications take advantage of Geode\u2019s scaling capabilities without changing their client code. Redis clients connect to a Geode server in the same way they connect to a Redis server, using an IP address and a port number.
-- **[Java Visual Statistics Display (JVSD)](../tools_modules/jvsd.html)**
-
- The Java Visual Statistics Display utility reads Geode statistics and produces graphical displays for analysis.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ada7dcb9/tools_modules/jvsd.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/jvsd.html.md.erb b/tools_modules/jvsd.html.md.erb
deleted file mode 100644
index 73f0ec9..0000000
--- a/tools_modules/jvsd.html.md.erb
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: Java Visual Statistics Display (JVSD)
----
-<a id="topic_523F6DE33FE54307BBE8F83BB7D9355D"></a>
-
-
-The Java Visual Statistics Display utility reads Geode statistics and produces graphical displays for analysis.
-
-- **[JVSD Overview](#jvsd-overview)**
-
-- **[Installing and Running JVSD](#installing-jvsd)**
-
-- **[Configure Statistics Sampling in Geode](#configure-statistics)**
-
-## JVSD Overview
-
-JVSD is an open source tool for review of the Geode metrics.
-
-## Installing and Running JVSD
-
-JVSD is available as a feature branch of the Geode repository. To install and run JVSD:
-
-1. Make sure that you have a recent checkout of Geode and that you are on the JVSD branch, `feature/GEODE-78`.
-
- ``` pre
- $ git status
- On branch feature/GEODE-78
- Your branch is up-to-date with 'origin/feature/GEODE-78'.
- nothing to commit, working directory clean
- ```
-
-2. Build the MultiAxisChart:
-
- ``` pre
- $ ./gradlew geode-jvsd:clean geode-jvsd:MultiAxisChart
- :geode-jvsd:clean
- :clean UP-TO-DATE
- :geode-jvsd:MultiAxisChartFX
- Cloning MultiAxisChartFX...
- Cloning MultiAxisChartFX... Done!
- Installing MultiAxisChartFX into local maven repository...
- Installing MultiAxisChartFX into local maven repository... Done!
-
- BUILD SUCCESSFUL
- ```
-
- At this point you should have the MultiAxisChart JAR file:
-
- ``` pre
- $ ls -la geode-jvsd/build/MultiAxisChartFX/target/MultiAxisChart-1.0-SNAPSHOT.jar
- -rw-r--r-- 1 jvuser staff 69979 Apr 1 07:21 geode-jvsd/build/MultiAxisChartFX/target/MultiAxisChart-1.0-SNAPSHOT.jar
- ```
-
- This JAR file should also now be installed in your local maven repository:
-
- ``` pre
- $ ls -la ~/.m2/repository/com/pivotal/javafx/MultiAxisChart/1.0-SNAPSHOT
- total 168
- drwxr-xr-x 6 jvuser staff 204 Apr 1 07:14 .
- drwxr-xr-x 4 jvuser staff 136 Apr 1 07:14 ..
- -rw-r--r-- 1 jvuser staff 69979 Apr 1 07:21 MultiAxisChart-1.0-SNAPSHOT.jar
- -rw-r--r-- 1 jvuser staff 1751 Apr 1 07:20 MultiAxisChart-1.0-SNAPSHOT.pom
- -rw-r--r-- 1 jvuser staff 201 Apr 1 07:21 _remote.repositories
- -rw-r--r-- 1 jvuser staff 712 Apr 1 07:21 maven-metadata-local.xml
- ```
-
-3. Build JVSD:
-
- ``` pre
- $ ./gradlew -x test geode-jvsd:installDist
- :geode-jvsd:MultiAxisChartFX SKIPPED
- :geode-jvsd:compileJava
- Note: Some input files use unchecked or unsafe operations.
- Note: Recompile with -Xlint:unchecked for details.
- :geode-jvsd:processResources
- :geode-jvsd:classes
- :geode-jvsd:jar
- :geode-jvsd:startScripts
- :geode-jvsd:installDist
-
- BUILD SUCCESSFUL
- ```
-
-4. Invoke JVSD from the command line:
-
- ``` pre
- $ ./geode-jvsd/build/install/geode-jvsd/bin/geode-jvsd
- ```
-
-<img src="../images/jVSD-startup.png" class="image" />
-
-## Configure Statistics Sampling in Geode
-
-Before you use JVSD, you must enable the collection of Geode statistics at runtime. Set the following configurations in gemfire.properties:
-
-``` pre
-statistic-sampling-enabled=true
-statistic-archive-file=myStats.gfs
-```
-
-Since collecting statistics at the default sampling rate of once every second does not affect performance, we recommend that sampling should always be enabled, including during development, testing, and in production.
-
-There is a special category of statistics called time-based statistics that can be very useful in troubleshooting and assessing the performance of some Geode operations, but they should be used with caution because their collection can affect performance. These statistics can be enabled using the following gemfire.properties configuration:
-
-``` pre
-enable-time-statistics=true
-```
-
-When the distributed system is up and running, every Geode instance generates a statistics file. To simplify browsing these statistics in JVSD, you may want to copy all the statistics files from all members into one directory so that you can easily load the files into JVSD.
-
-
[11/50] [abbrv] incubator-geode git commit: Integrated Security:
complete section on the properties that enable the security callbacks.
[#129578041]
Posted by rv...@apache.org.
Integrated Security: complete section on the properties
that enable the security callbacks. [#129578041]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/bce4a113
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/bce4a113
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/bce4a113
Branch: refs/staging/docs-grant1
Commit: bce4a1133881a329841f2bad672fc1cfa4d8c73d
Parents: 8a56847
Author: Karen Miller <km...@pivotal.io>
Authored: Thu Sep 1 14:54:09 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Thu Sep 1 14:54:09 2016 -0700
----------------------------------------------------------------------
managing/security/enable_security.html.md.erb | 57 +++++++++++++++++-----
1 file changed, 45 insertions(+), 12 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/bce4a113/managing/security/enable_security.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/enable_security.html.md.erb b/managing/security/enable_security.html.md.erb
index b4c1c6b..b281ea9 100644
--- a/managing/security/enable_security.html.md.erb
+++ b/managing/security/enable_security.html.md.erb
@@ -3,9 +3,12 @@ title: Enable Security with Property Definitions
---
-The callbacks that implement the authorization of an application
+## security-manager Property
+
+The callbacks that implement the authentication and authorization
+of the various components of the system
are specified with the `security-manager` property.
-When this property is defined, authorization is enabled.
+When this property is defined, authentication and authorization are enabled.
The definition of the `security-manager` property is the
path to the implementation of the `SecurityManager` interface.
For example:
@@ -14,19 +17,27 @@ For example:
security-manager = com.example.security.MySecurityManager
```
-All components of the system invoke the same callback.
-Authorization may be enabled on a component basis with
+## security-enabled-components Property
+
+All components of the system invoke the same callbacks.
+Security may be enabled on a component basis with
the definition of the `security-enabled-components` property.
Its definition restricts which system components invoke
-the authorization callback.
+the authentication and authorization callbacks.
+The defined values for system components:
-- `all`. All components invoke the `authorize` callback.
-- `server`.
-- `cluster`.
-- `jmx`. Invokes the `authorize` callback for all components
-that ?
-- `http`.
-- `gateway`.
+- `all`. All components invoke the security callbacks.
+- `server`. Invokes security callbacks upon connection and operation
+requests that a client makes of a server.
+- `cluster`. Invokes security callbacks upon connection and operation
+requests that a server makes as the peer of a locator.
+- `jmx`. Invokes security callbacks upon connection and operation
+requests that components communicating with a JMX manager make of a locator.
+Both `gfsh` and `Pulse` use this form of communication.
+- `http`. Invokes security callbacks upon connection and operation
+requests that applications communicating via the REST API make of a server.
+- `gateway`. Invokes security callbacks upon connection and operation
+requests that a gateway sender makes of a locator.
The `security-enabled-components` property defines
a comma-separated list of components that will
@@ -36,6 +47,28 @@ For example,
``` pre
security-enabled-components = server, cluster jmx
```
+
+The `all` component value is used by itself, as in the example
+
+``` pre
+security-enabled-components = all
+```
+
+## security-post-processor Property
+
+The `PostProcessor` interface allows the definition of a set of callbacks
+that are invoked after operations that get data,
+but before the data is returned.
+This permits the callback to intervene and modify of the data
+that is to be returned.
+The callbacks do not modify the region data,
+only the data to be returned.
+
+Enable the post processing of data by defining the
+`security-post-processor` property
+with the path to the definition of the interface.
+For example,
+
``` pre
security-post-processor = com.example.security.MySecurityPostProcessing
```
[04/50] [abbrv] incubator-geode git commit: Merge branch
'feature/IntegratedSecurity' of https://github.com/gemfire/docs-geode-md into
feature/IntegratedSecurity
Posted by rv...@apache.org.
Merge branch 'feature/IntegratedSecurity' of https://github.com/gemfire/docs-geode-md into feature/IntegratedSecurity
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/6a5c86de
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/6a5c86de
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/6a5c86de
Branch: refs/staging/docs-grant1
Commit: 6a5c86de032b29e95556266606054edd3a76f22c
Parents: f9b76d5 894762c
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Aug 31 15:55:30 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Aug 31 15:55:30 2016 -0700
----------------------------------------------------------------------
managing/security/implementing_ssl.html.md.erb | 61 +--------------------
1 file changed, 1 insertion(+), 60 deletions(-)
----------------------------------------------------------------------
[42/50] [abbrv] incubator-geode git commit: Merge remote-tracking
branch 'origin/develop' into feature/IntegratedSecurity
Posted by rv...@apache.org.
Merge remote-tracking branch 'origin/develop' into feature/IntegratedSecurity
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/d12bc235
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/d12bc235
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/d12bc235
Branch: refs/staging/docs-grant1
Commit: d12bc23576192719c69b9deab6417ca3bfa34bb5
Parents: b7f3078 2bd8128
Author: Karen Miller <km...@pivotal.io>
Authored: Tue Sep 20 17:23:15 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Tue Sep 20 17:23:15 2016 -0700
----------------------------------------------------------------------
.../cluster_config/gfsh_remote.html.md.erb | 1 +
.../data_serialization_options.html.md.erb | 4 ++++
.../extending_the_autoserializer.html.md.erb | 2 +-
.../gemfire_data_serialization.html.md.erb | 2 +-
...iguring_gateway_concurrency_levels.html.md.erb | 2 +-
...menting_write_behind_event_handler.html.md.erb | 4 ++--
.../function_exec/chapter_overview.html.md.erb | 5 +++--
.../function_exec/function_execution.html.md.erb | 2 +-
.../using_query_bind_parameters.html.md.erb | 2 +-
.../query_index/maintaining_indexes.html.md.erb | 2 +-
.../query_select/the_select_statement.html.md.erb | 2 +-
.../querying_partitioned_regions.html.md.erb | 6 +++---
.../querying_basics/running_a_query.html.md.erb | 4 ++--
.../working_with_transactions.html.md.erb | 2 +-
.../querying_quick_reference.html.md.erb | 4 ++--
managing/security/implementing_ssl.html.md.erb | 18 +++++++++---------
.../http_session_mgmt/quick_start.html.md.erb | 4 ++--
17 files changed, 36 insertions(+), 30 deletions(-)
----------------------------------------------------------------------
[43/50] [abbrv] incubator-geode git commit: Draft of OQL aggregates
documentation. [#130418485]
Posted by rv...@apache.org.
Draft of OQL aggregates documentation. [#130418485]
- Needs revision to implement formatting/style/prose to
indicate its experimental status.
- Incomplete: changes not incoporporated into the grammar
definition, because the grammar is not up to date.
- Examples should be added (and verified) for each of the functions.
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/e1ffcd10
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/e1ffcd10
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/e1ffcd10
Branch: refs/staging/docs-grant1
Commit: e1ffcd10a9d90671465a5f961d9d908fa00c9334
Parents: d12bc23
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Sep 21 14:00:15 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Sep 21 14:00:15 2016 -0700
----------------------------------------------------------------------
.../the_select_statement.html.md.erb | 118 +++++++++++++++++++
...ictions_and_unsupported_features.html.md.erb | 14 ++-
2 files changed, 130 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e1ffcd10/developing/query_select/the_select_statement.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/query_select/the_select_statement.html.md.erb b/developing/query_select/the_select_statement.html.md.erb
index 04d14df..04f9f3b 100644
--- a/developing/query_select/the_select_statement.html.md.erb
+++ b/developing/query_select/the_select_statement.html.md.erb
@@ -201,3 +201,121 @@ FROM /exampleRegion p, p.positions.values pos
WHERE p.ID > 0 OR p.status = 'active' OR pos.secId
OR pos.secId = 'IBM'
```
+
+<div style="background-color:lightyellow;">
+<h2>(Experimental Feature) Aggregate Functions</h2>
+
+<p>
+Some prose here about being experimental.
+</p>
+
+<p>
+The aggregate functions
+<code>MIN</code>,
+<code>MAX</code>,
+<code>AVG</code>,
+<code>AVG</code> over a DISTINCT expression,
+<code>SUM</code> over a DISTINCT expression,
+<code>COUNT</code>, and
+<code>COUNT</code> over a DISTINCT expression
+are supported.
+The <code>GROUP BY</code> extension is also supported where appropriate.
+</p>
+
+<p>
+The <code>MIN</code> function returns the smallest of the selected
+expression.
+The type of the expression must evaluate to a
+<code>java.lang.Comparable</code>.
+</p>
+
+<p>
+The <code>MAX</code> function returns the largest of the selected
+expression.
+The type of the expression must evaluate to a
+<code>java.lang.Comparable</code>.
+</p>
+
+<p>
+The <code>AVG</code> function returns the arithmetic mean of the set
+formed by the selected expression.
+The type of the expression must evaluate to a
+<code>java.lang.Number</code>.
+For partitioned regions,
+each node's buckets provide both a sum and the number of elements
+to the node executing the query,
+such that a correct average may be computed.
+</p>
+
+<p>
+The <code>AVG</code> function where the DISTINCT modifier is applied
+to the expression returns the arithmetic mean of the set
+of unique (distinct) values.
+The type of the expression must evaluate to a
+<code>java.lang.Number</code>.
+For partitioned regions,
+the distinct values in a node's buckets are returned
+to the node executing the query.
+The query node can then calculate the avarage over
+the values that are unique across nodes,
+after eliminating duplicate values that come from separate nodes.
+</p>
+
+<p>
+The <code>SUM</code> function returns the sum over the set
+formed by the selected expression.
+The type of the expression must evaluate to a
+<code>java.lang.Number</code>.
+For partitioned regions,
+each node's buckets compute a sum over that node,
+returning that sum
+to the node executing the query,
+when then sums across all nodes.
+</p>
+
+<p>
+The <code>SUM</code> function where the DISTINCT modifier is applied
+to the expression returns the sum over the set
+of unique (distinct) values.
+The type of the expression must evaluate to a
+<code>java.lang.Number</code>.
+For partitioned regions,
+the distinct values in a node's buckets are returned
+to the node executing the query.
+The query node can then calculate the sum over
+the values that are unique across nodes,
+after eliminating duplicate values that come from separate nodes.
+</p>
+
+<p>
+The <code>COUNT</code> function returns the quantity of values in the set
+formed by the selected expression.
+For example, to return the quantity of employees who have a
+positive sales amount:
+</p>
+<pre>
+SELECT count(e.sales) FROM /employees e WHERE e.sales > 0.0
+</pre>
+<p>
+The <code>COUNT</code> function where the DISTINCT modifier is applied
+returns the quantity of unique (distinct) values in the set
+formed by the selected expression.
+</p>
+</div>
+
+<div style="background-color:lightyellow;">
+<h2>(Experimental Feature) GROUP BY Extension for Aggregate Functions</h2>
+
+<p>
+<code>GROUP BY</code> is required
+when aggregate functions are used in combination
+with other selected items.
+It permits ordering.
+For example,
+</p>
+
+<pre>
+SELECT ID, MAX(e.sales) FROM /employees e GROUP BY ID
+</pre>
+
+</div>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e1ffcd10/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb b/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
index 31a49b6..baac020 100644
--- a/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
+++ b/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
@@ -4,7 +4,6 @@ title: Query Language Restrictions and Unsupported Features
At a high level, Geode does not support the following querying features:
-- GROUPBY is not supported.
- Indexes targeted for joins across more than one region are not supported
- Static method invocations. For example, the following query is invalid:
@@ -12,10 +11,21 @@ At a high level, Geode does not support the following querying features:
SELECT DISTINCT * FROM /QueryRegion0 WHERE aDay = Day.Wednesday
```
-- Aggregate functions are not supported.
- You cannot create an index on fields using Set/List types (Collection types) that are not comparable. The OQL index implementation expects fields to be Comparable. To workaround this, you can create a custom Collection type that implements Comparable.
- ORDER BY is only supported with DISTINCT queries.
In addition, there are some specific limitations on partitioned region querying. See [Partitioned Region Query Restrictions](../query_additional/partitioned_region_query_restrictions.html#concept_5353476380D44CC1A7F586E5AE1CE7E8).
+<div style="background-color:lightyellow;">
+<h2> Features Supported on an Experimental Basis</h2>
+<p>
+These features are supported,
+but their experimental implementation may change:
+</p>
+
+<ul>
+<li> GROUP BY
+<li> The aggregate functions AVG, MIN, MAX, COUNT, SUM
+</ul>
+</div>
[38/50] [abbrv] incubator-geode git commit: Update SSL: replace
'http' component with 'web' [#130656307]
Posted by rv...@apache.org.
Update SSL: replace 'http' component with 'web' [#130656307]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/a432d8eb
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/a432d8eb
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/a432d8eb
Branch: refs/staging/docs-grant1
Commit: a432d8eb69355bdc39d8183c4a7116b7ee3c6e2a
Parents: 8efe9fb
Author: Dave Barnes <db...@pivotal.io>
Authored: Mon Sep 19 17:31:14 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Mon Sep 19 17:31:14 2016 -0700
----------------------------------------------------------------------
managing/security/implementing_ssl.html.md.erb | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/a432d8eb/managing/security/implementing_ssl.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_ssl.html.md.erb b/managing/security/implementing_ssl.html.md.erb
index 7792c79..73bbf49 100644
--- a/managing/security/implementing_ssl.html.md.erb
+++ b/managing/security/implementing_ssl.html.md.erb
@@ -18,8 +18,8 @@ to communicate using SSL, and the kind of communications to which each component
<dt>**gateway**</dt>
<dd>Communication across WAN gateways from one site to another</dd>
-<dt>**http**</dt>
-<dd>All HTTP-based services hosted on the configured server, which can include the Developer REST API
+<dt>**web**</dt>
+<dd>All web-based services hosted on the configured server, which can include the Developer REST API
service, the Management REST API service (used for remote cluster management) and the Pulse
monitoring tool's web-based user interface.</dd>
@@ -52,10 +52,10 @@ protocols, and to provide the location and credentials for key and trust stores.
<dd>list of components for which to enable SSL. "all" or comma-separated list of components</dd>
<dt>**ssl-require-authentication**</dt>
-<dd>Requires two-way authentication, applies to all components except http. boolean - if true (the default), two-way authentication is required.</dd>
+<dd>Requires two-way authentication, applies to all components except web. boolean - if true (the default), two-way authentication is required.</dd>
-<dt>**ssl-http-require-authentication**</dt>
-<dd>Requires two-way authentication for http component. boolean - if true, two-way authentication is required. Default is false (one-way authentication only).</dd>
+<dt>**ssl-web-require-authentication**</dt>
+<dd>Requires two-way authentication for web component. boolean - if true, two-way authentication is required. Default is false (one-way authentication only).</dd>
<dt>**ssl-default-alias**</dt>
<dd>A server uses one key store to hold its SSL certificates. All components on that server can share a
@@ -156,7 +156,7 @@ The following table lists the components you can configure to use SSL.
|-----------|-----------------------------------------------------------------------|
| cluster | Peer-to-peer communications among members of a distributed system |
| gateway | Communication across WAN gateways from one site to another |
-| http | Hypertext transport protocol communication, including REST interfaces |
+| web | Web-based communication, including REST interfaces |
| jmx | Java management extension communications, including gfsh |
| locator | Communication with and between locators |
| server | Communication between clients and servers |
@@ -168,9 +168,9 @@ The following table lists the properties you can use to configure SSL on your Ge
| Property | Description | Value |
|------------------------------------|------------------------------------------------------------------------------|-------|
-| ssl‑enabled‑components | list of components for which to enable SSL | "all" or comma-separated list of components: cluster, gateway, http, jmx, locator, server |
-| ssl-require-authentication | requires two-way authentication, applies to all components except http | boolean - if true (the default), two-way authentication is required |
-| ssl‑http‑require‑authentication | requires two-way authentication for http component | boolean - if true, two-way authentication is required. Default is false (one-way authentication only) |
+| ssl‑enabled‑components | list of components for which to enable SSL | "all" or comma-separated list of components: cluster, gateway, web, jmx, locator, server |
+| ssl-require-authentication | requires two-way authentication, applies to all components except web | boolean - if true (the default), two-way authentication is required |
+| ssl‑web‑require‑authentication | requires two-way authentication for web component | boolean - if true, two-way authentication is required. Default is false (one-way authentication only) |
| ssl-default-alias | default certificate name | string - if empty, use first certificate in key store |
| ssl-_component_-alias | component-specific certificate name | string - applies to specified _component_ |
| ssl-ciphers | list of SSL ciphers | comma-separated list (default "any") |
[50/50] [abbrv] incubator-geode git commit: Revert "Add empty
sections as placeholders for automated rebalance"
Posted by rv...@apache.org.
Revert "Add empty sections as placeholders for automated rebalance"
This reverts commit 6b8d375a62de178a7815cf234d20f58169b7c33b.
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/2eabdb2d
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/2eabdb2d
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/2eabdb2d
Branch: refs/staging/docs-grant1
Commit: 2eabdb2d7d3a04b2f96adcd714cb000a2d41a399
Parents: 2f1e5f5
Author: Karen Miller <km...@pivotal.io>
Authored: Thu Sep 29 10:31:27 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Thu Sep 29 10:31:27 2016 -0700
----------------------------------------------------------------------
developing/partitioned_regions/automated_rebalance.html.md.erb | 6 ------
developing/partitioned_regions/chapter_overview.html.md.erb | 4 ----
2 files changed, 10 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/2eabdb2d/developing/partitioned_regions/automated_rebalance.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/partitioned_regions/automated_rebalance.html.md.erb b/developing/partitioned_regions/automated_rebalance.html.md.erb
deleted file mode 100644
index d134b8c..0000000
--- a/developing/partitioned_regions/automated_rebalance.html.md.erb
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Automated Rebalancing
----
-
-What it is and how it works.
-
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/2eabdb2d/developing/partitioned_regions/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/partitioned_regions/chapter_overview.html.md.erb b/developing/partitioned_regions/chapter_overview.html.md.erb
index 26579c2..56e65e1 100644
--- a/developing/partitioned_regions/chapter_overview.html.md.erb
+++ b/developing/partitioned_regions/chapter_overview.html.md.erb
@@ -32,10 +32,6 @@ In addition to basic region management, partitioned regions include options for
In a distributed system with minimal contention to the concurrent threads reading or updating from the members, you can use rebalancing to dynamically increase or decrease your data and processing capacity.
-- **[Automated Rebalancing](../../developing/partitioned_regions/automated_rebalance.html)**
-
- Short description of automated rebalancing.
-
- **[Checking Redundancy in Partitioned Regions](../../developing/partitioned_regions/checking_region_redundancy.html)**
Under some circumstances, it can be important to verify that your partitioned region data is redundant and that upon member restart, redundancy has been recovered properly across partitioned region members.
[31/50] [abbrv] incubator-geode git commit: Merge remote-tracking
branch 'origin/develop' into feature/IntegratedSecurity
Posted by rv...@apache.org.
Merge remote-tracking branch 'origin/develop' into feature/IntegratedSecurity
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/d19a977e
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/d19a977e
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/d19a977e
Branch: refs/staging/docs-grant1
Commit: d19a977ed5474a931fb8fbb6098437db64864c4d
Parents: 17399f0 66a81e8
Author: Karen Miller <km...@pivotal.io>
Authored: Tue Sep 13 16:28:39 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Tue Sep 13 16:28:39 2016 -0700
----------------------------------------------------------------------
.../gfsh/command-pages/echo.html.md.erb | 26 ++++++--------------
.../http_session_mgmt/quick_start.html.md.erb | 7 +++---
.../tc_installing_the_module.html.md.erb | 2 +-
3 files changed, 11 insertions(+), 24 deletions(-)
----------------------------------------------------------------------
[15/50] [abbrv] incubator-geode git commit: Region shortcuts:
consistent capitalization and use of underscore for data-policy
specifications [#116783515]
Posted by rv...@apache.org.
Region shortcuts: consistent capitalization and use of underscore for data-policy specifications [#116783515]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/27455f03
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/27455f03
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/27455f03
Branch: refs/staging/docs-grant1
Commit: 27455f038afc110f84f6e9bacef28547baa9fa7f
Parents: 51f43fa
Author: Dave Barnes <db...@pivotal.io>
Authored: Tue Sep 6 16:55:01 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Tue Sep 6 16:55:01 2016 -0700
----------------------------------------------------------------------
.../region_shortcuts_reference.html.md.erb | 20 ++++++-------
.../topics/region_shortcuts_table.html.md.erb | 30 ++++++++++----------
2 files changed, 25 insertions(+), 25 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/27455f03/reference/topics/region_shortcuts_reference.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/region_shortcuts_reference.html.md.erb b/reference/topics/region_shortcuts_reference.html.md.erb
index 0104aa1..c10da71 100644
--- a/reference/topics/region_shortcuts_reference.html.md.erb
+++ b/reference/topics/region_shortcuts_reference.html.md.erb
@@ -207,7 +207,7 @@ For more information, see:
| | |
|----|----|
| scope: | local |
-| data-policy: | PERSISTENT-REPLICATE |
+| data-policy: | PERSISTENT_REPLICATE |
### <a id="reference_l5r_y4y_lk__section_E41981F332664D48A3914D4BEEC50902" class="no-quick-link"></a>gfsh Command Example
@@ -260,7 +260,7 @@ For more information, see:
| | |
|----|----|
| scope: | local |
-| data-policy: | PERSISTENT-REPLICATE |
+| data-policy: | PERSISTENT_REPLICATE |
<span class="keyword parmname">Eviction Attributes</span>
@@ -516,7 +516,7 @@ For more information, see:
| | |
|----|----|
-| data-policy: | PERSISTENT-PARTITION |
+| data-policy: | PERSISTENT_PARTITION |
### <a id="reference_d4k_jpy_lk__section_F2B651B4803341E3991F554544EF8551" class="no-quick-link"></a>gfsh Command Example
@@ -568,7 +568,7 @@ For more information, see:
| | |
|----|----|
-| data-policy: | PERSISTENT-PARTITION |
+| data-policy: | PERSISTENT_PARTITION |
<span class="keyword parmname">Eviction Attributes</span>
@@ -976,7 +976,7 @@ For more information, see:
| | |
|----|----|
-| data-policy: | PERSISTENT-PARTITION |
+| data-policy: | PERSISTENT_PARTITION |
<span class="keyword parmname">Partition Attributes</span>
@@ -1038,7 +1038,7 @@ For more information, see:
| | |
|----|----|
-| data-policy: | PERSISTENT-PARTITION |
+| data-policy: | PERSISTENT_PARTITION |
<span class="keyword parmname">Eviction Attributes</span>
@@ -1161,7 +1161,7 @@ For more information, see:
| | |
|----|----|
| scope: | distributed-ack |
-| data-policy: | preloaded |
+| data-policy: | PRELOADED |
<span class="keyword parmname">Eviction Attributes</span>
@@ -1253,7 +1253,7 @@ For more information, see:
| | |
|----|----|
| scope: | distributed-ack |
-| data-policy: | replicate |
+| data-policy: | REPLICATE |
<span class="keyword parmname">Eviction Attributes</span>
@@ -1321,7 +1321,7 @@ For more information, see:
| | |
|----|----|
| scope: | distributed-ack |
-| data-policy: | PERSISTENT-REPLICATE |
+| data-policy: | PERSISTENT_REPLICATE |
### <a id="reference_emp_jpy_lk__section_71C90F066BDC4013B8AB7B68D4766B5B" class="no-quick-link"></a>gfsh Command Example
@@ -1375,7 +1375,7 @@ For more information, see:
| | |
|----|----|
| scope: | distributed-ack |
-| data-policy: | PERSISTENT-REPLICATE |
+| data-policy: | PERSISTENT_REPLICATE |
<span class="keyword parmname">Eviction Attributes</span>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/27455f03/reference/topics/region_shortcuts_table.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/region_shortcuts_table.html.md.erb b/reference/topics/region_shortcuts_table.html.md.erb
index a7607f0..b73f9af 100644
--- a/reference/topics/region_shortcuts_table.html.md.erb
+++ b/reference/topics/region_shortcuts_table.html.md.erb
@@ -28,7 +28,7 @@ This section provides a quick reference for all region shortcuts.
<td><p><a href="region_shortcuts_reference.html#reference_w2h_3cd_lk)">LOCAL</a></p></td>
<td><div id="reference_ufj_5kz_4k__p_q44_t11_nk" class="p">
scope:
-local
+local<br />
data-policy:
NORMAL
</div></td>
@@ -38,7 +38,7 @@ NORMAL
<td><p><a href="region_shortcuts_reference.html#reference_wd5_lpy_lk">LOCAL_HEAP_LRU</a></p></td>
<td><div id="reference_ufj_5kz_4k__p_axf_z11_nk" class="p">
scope:
-local
+local<br />
data-policy:
NORMAL
</div></td>
@@ -62,7 +62,7 @@ NORMAL
<td><p>[LOCAL_OVERFLOW](region_shortcuts_reference.html#reference_adk_y4y_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_fsq_jc1_nk" class="p">
scope:
-local
+local<br />
data-policy:
NORMAL
</div></td>
@@ -86,9 +86,9 @@ NORMAL
<td><p>[LOCAL_PERSISTENT](region_shortcuts_reference.html#reference_l5r_y4y_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_ctq_jc1_nk" class="p">
scope:
-local
+local<br />
data-policy:
-PERSISTENT-REPLICATE
+PERSISTENT\_REPLICATE
</div></td>
<td>�</td>
</tr>
@@ -96,9 +96,9 @@ PERSISTENT-REPLICATE
<td><p>[LOCAL\_PERSISTENT\_OVERFLOW](region_shortcuts_reference.html#reference_a45_y4y_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_ttq_jc1_nk" class="p">
scope:
-local
+local<br />
data-policy:
-PERSISTENT-REPLICATE
+PERSISTENT\_REPLICATE
</div></td>
<td><p><span class="keyword parmname">Eviction Attributes</span></p>
<div id="reference_ufj_5kz_4k__p_e5q_jc1_nk" class="p">
@@ -172,7 +172,7 @@ PARTITION
<td><p>[PARTITION_PERSISTENT](region_shortcuts_reference.html#reference_d4k_jpy_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_qwq_jc1_nk" class="p">
data-policy:
-PERSISTENT-PARTITION
+PERSISTENT\_PARTITION
</div></td>
<td>�</td>
</tr>
@@ -180,7 +180,7 @@ PERSISTENT-PARTITION
<td><p>[PARTITION\_PERSISTENT\_OVERFLOW](region_shortcuts_reference.html#reference_v5l_jpy_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_axq_jc1_nk" class="p">
data-policy:
-PERSISTENT-PARTITION
+PERSISTENT\_PARTITION
</div></td>
<td><p><span class="keyword parmname">Eviction Attributes</span></p>
<div id="reference_ufj_5kz_4k__p_lxq_jc1_nk" class="p">
@@ -326,7 +326,7 @@ PARTITION
<td><p>[PARTITION\_REDUNDANT\_PERSISTENT](region_shortcuts_reference.html#reference_bd4_jpy_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_jbr_jc1_nk" class="p">
data-policy:
-PERSISTENT-PARTITION
+PERSISTENT\_PARTITION
</div></td>
<td><div id="reference_ufj_5kz_4k__p_pbr_jc1_nk" class="p">
<span class="keyword parmname">Partition Attributes</span>
@@ -344,7 +344,7 @@ PERSISTENT-PARTITION
<td><p>[PARTITION\_REDUNDANT\_PERSISTENT_OVERFLOW](region_shortcuts_reference.html#reference_xqq_tvc_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_xbr_jc1_nk" class="p">
data-policy:
-PERSISTENT-PARTITION
+PERSISTENT\_PARTITION
</div></td>
<td><p><span class="keyword parmname">Eviction Attributes</span></p>
<div id="reference_ufj_5kz_4k__p_fcr_jc1_nk" class="p">
@@ -387,7 +387,7 @@ distributed-ack
<td><p>[REPLICATE\_HEAP\_LRU](region_shortcuts_reference.html#reference_xx4_jpy_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_cdr_jc1_nk" class="p">
data-policy:
-preloaded
+PRELOADED
scope:
distributed-ack
</div></td>
@@ -430,7 +430,7 @@ distributed-ack
<td><p>[REPLICATE_OVERFLOW](region_shortcuts_reference.html#reference_t2p_jpy_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_wdr_jc1_nk" class="p">
data-policy:
-replicate
+REPLICATE
scope:
distributed-ack
</div></td>
@@ -454,7 +454,7 @@ distributed-ack
<td><p>[REPLICATE_PERSISTENT](region_shortcuts_reference.html#reference_emp_jpy_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_n2r_jc1_nk" class="p">
data-policy:
-PERSISTENT-REPLICATE
+PERSISTENT\_REPLICATE
scope:
distributed-ack
</div></td>
@@ -464,7 +464,7 @@ distributed-ack
<td><p>[REPLICATE\_PERSISTENT\_OVERFLOW](region_shortcuts_reference.html#reference_tsp_jpy_lk)</p></td>
<td><div id="reference_ufj_5kz_4k__p_w2r_jc1_nk" class="p">
data-policy:
-PERSISTENT-REPLICATE
+PERSISTENT\_REPLICATE
scope:
distributed-ack
</div></td>
[03/50] [abbrv] incubator-geode git commit: Correcting conflict
resolution error from preceding merge
Posted by rv...@apache.org.
Correcting conflict resolution error from preceding merge
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/894762c8
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/894762c8
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/894762c8
Branch: refs/staging/docs-grant1
Commit: 894762c8e8597a6055f4f13bb730e08e869fe590
Parents: 590a372
Author: Dave Barnes <db...@pivotal.io>
Authored: Wed Aug 31 15:51:59 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Wed Aug 31 15:51:59 2016 -0700
----------------------------------------------------------------------
managing/security/implementing_ssl.html.md.erb | 61 +--------------------
1 file changed, 1 insertion(+), 60 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/894762c8/managing/security/implementing_ssl.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_ssl.html.md.erb b/managing/security/implementing_ssl.html.md.erb
index f30bbc8..7792c79 100644
--- a/managing/security/implementing_ssl.html.md.erb
+++ b/managing/security/implementing_ssl.html.md.erb
@@ -6,66 +6,7 @@ You can configure SSL for authentication between members and to protect your dat
distribution. You can use SSL alone or in conjunction with the other Geode security options.
Geode SSL connections use the Java Secure Sockets Extension (JSSE) package.
-## Gateway SSL Configuration
-
-The following table lists the SSL configuration property names used to configure SSL for peer-to-peer and WAN gateway connections. Remember that if you do not define a client/server, JMX, or WAN property, then Geode uses the property value defined for peer-to-peer communication (cluster-ssl\*) or the default peer-to-peer property value if unspecified.
-
-<a id="concept_65874F58A47C4D10B29248BBF0635BFC__table_jpw_wqr_n4"></a>
-
-<table>
-<caption><span class="tablecap">Table 2. SSL Configuration Property Names by Connection Type</span></caption>
-<colgroup>
-<col width="50%" />
-<col width="50%" />
-</colgroup>
-<thead>
-<tr class="header">
-<th>Peer-to-Peer Connection Property
-<p>(provides default value for all other connection types)</p></th>
-<th>WAN Gateway Connection Property</th>
-</tr>
-</thead>
-<tbody>
-<tr class="odd">
-<td>cluster-ssl-enabled</td>
-<td>gateway-ssl-enabled</td>
-</tr>
-<tr class="even">
-<td>cluster-ssl-ciphers</td>
-<td>gateway-ssl-ciphers</td>
-</tr>
-<tr class="odd">
-<td>cluster-ssl-protocols</td>
-<td>gateway-ssl-protocols</td>
-</tr>
-<tr class="even">
-<td>cluster-ssl-require-authentication</td>
-<td>gateway-ssl-require-authentication</td>
-</tr>
-<tr class="odd">
-<td>cluster-ssl-keystore-type</td>
-<td>gateway-ssl-keystore-type</td>
-</tr>
-<tr class="even">
-<td>cluster-ssl-keystore</td>
-<td>gateway-ssl-keystore</td>
-</tr>
-<tr class="odd">
-<td>cluster-ssl-keystore-password</td>
-<td>gateway-ssl-keystore-password</td>
-</tr>
-<tr class="even">
-<td>cluster-ssl-truststore</td>
-<td>gateway-ssl-truststore</td>
-</tr>
-<tr class="odd">
-<td>cluster-ssl-keystore-password</td>
-<td>gateway-ssl-keystore-password</td>
-</tr>
-</tbody>
-</table>
-
-If you configure the above peer-to-peer SSL properties, then by default Geode uses the same SSL property values for all stream-socket communication. This includes communication between cache servers and clients, between the JMX manager and JMX clients, and between two Geode distributed systems connected by a WAN gateway.
+## <a id="ssl_configurable_components" class="no-quick-link"></a>SSL-Configurable Components
You can specify that SSL be used system-wide, or you can independently configure SSL for specific
system components. The following list shows the system components that can be separately configured
[36/50] [abbrv] incubator-geode git commit: Implement changes based
on Swap's feedback on the integrated security section [#130653929]
Posted by rv...@apache.org.
Implement changes based on Swap's feedback on the integrated
security section [#130653929]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/e3196ed1
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/e3196ed1
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/e3196ed1
Branch: refs/staging/docs-grant1
Commit: e3196ed1bb21e1227ffca9a7f8584fc47615c6a5
Parents: b60f78a
Author: Karen Miller <km...@pivotal.io>
Authored: Mon Sep 19 14:11:22 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Mon Sep 19 14:11:22 2016 -0700
----------------------------------------------------------------------
managing/security/enable_security.html.md.erb | 6 +++---
managing/security/implementing_security.html.md.erb | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e3196ed1/managing/security/enable_security.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/enable_security.html.md.erb b/managing/security/enable_security.html.md.erb
index 8f2824c..c6b4e33 100644
--- a/managing/security/enable_security.html.md.erb
+++ b/managing/security/enable_security.html.md.erb
@@ -5,12 +5,12 @@ title: Enable Security with Property Definitions
## security-manager Property
-The callbacks that implement the authentication and authorization
-of the various components of the system
+The authentication callback and the authorization callback that implement
+the `SecurityManager` interface
are specified with the `security-manager` property.
When this property is defined, authentication and authorization are enabled.
The definition of the `security-manager` property is the
-path to the implementation of the `SecurityManager` interface.
+fully qualified name of the class that implements the `SecurityManager` interface.
For example:
``` pre
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e3196ed1/managing/security/implementing_security.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_security.html.md.erb b/managing/security/implementing_security.html.md.erb
index 4400af3..a38dd03 100644
--- a/managing/security/implementing_security.html.md.erb
+++ b/managing/security/implementing_security.html.md.erb
@@ -30,7 +30,7 @@ data in transit.
Authentication verifies the identity of communicating components,
leading to control over participation.
-The variety of participants include peer members, cache servers,
+The variety of participants include peer members, servers,
clients, originators of JMX operations, Pulse,
gateway senders and receivers representing WAN members of the system,
and commands arriving from `gfsh` on behalf of system users
[49/50] [abbrv] incubator-geode git commit: Remove JVSD docs from
user guide (followup - remove a graphic) [#130994985]
Posted by rv...@apache.org.
Remove JVSD docs from user guide (followup - remove a graphic) [#130994985]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/2f1e5f5b
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/2f1e5f5b
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/2f1e5f5b
Branch: refs/staging/docs-grant1
Commit: 2f1e5f5b819c77d9e0af16b28afe2682b7b1daf9
Parents: 6b8d375
Author: Dave Barnes <db...@pivotal.io>
Authored: Thu Sep 29 10:00:22 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Thu Sep 29 10:00:22 2016 -0700
----------------------------------------------------------------------
images/jVSD-startup.png | Bin 32647 -> 0 bytes
1 file changed, 0 insertions(+), 0 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/2f1e5f5b/images/jVSD-startup.png
----------------------------------------------------------------------
diff --git a/images/jVSD-startup.png b/images/jVSD-startup.png
deleted file mode 100644
index d4d81a9..0000000
Binary files a/images/jVSD-startup.png and /dev/null differ
[08/50] [abbrv] incubator-geode git commit: Add new integrated
security subsection on post processing.
Posted by rv...@apache.org.
Add new integrated security subsection on post processing.
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/705677d1
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/705677d1
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/705677d1
Branch: refs/staging/docs-grant1
Commit: 705677d183a8b058c68852935c0dd7676835a3bf
Parents: 1ecc0eb
Author: Karen Miller <km...@pivotal.io>
Authored: Thu Sep 1 09:45:54 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Thu Sep 1 09:45:54 2016 -0700
----------------------------------------------------------------------
managing/security/chapter_overview.html.md.erb | 2 ++
managing/security/post_processing.html.md.erb | 12 ++++++++++++
2 files changed, 14 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/705677d1/managing/security/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/chapter_overview.html.md.erb b/managing/security/chapter_overview.html.md.erb
index 9269bd6..d1636a3 100644
--- a/managing/security/chapter_overview.html.md.erb
+++ b/managing/security/chapter_overview.html.md.erb
@@ -27,6 +27,8 @@ features help to secure the distributed system.
Client operations on a cache server can be restricted or completely blocked based on the roles and permissions assigned to the credentials submitted by the client.
+- **[Post Processing of Region Data](../../managing/security/post_processing.html)**
+
- **[SSL](../../managing/security/ssl_overview.html)**
SSL protects your data in transit between applications.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/705677d1/managing/security/post_processing.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/post_processing.html.md.erb b/managing/security/post_processing.html.md.erb
new file mode 100644
index 0000000..8b04380
--- /dev/null
+++ b/managing/security/post_processing.html.md.erb
@@ -0,0 +1,12 @@
+---
+title: Post Processing of Region Data
+---
+
+The `PostProcessor` interface allows the definition of a set of callbacks
+that are invoked after operations that get data,
+but before the data is returned.
+This permits the callback to intervene and modify of the data
+that is to be returned.
+The callbacks do not modify the region data,
+only the data to be returned.
+
[32/50] [abbrv] incubator-geode git commit: Remove
security-enabled-components property and rework prose to accomodate the
removal. [#130304427]
Posted by rv...@apache.org.
Remove security-enabled-components property and rework prose
to accomodate the removal. [#130304427]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/b40485b0
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/b40485b0
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/b40485b0
Branch: refs/staging/docs-grant1
Commit: b40485b02d2c75b6114ef549fe017f5578255b64
Parents: d19a977
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Sep 14 09:39:48 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Sep 14 09:39:48 2016 -0700
----------------------------------------------------------------------
managing/security/enable_security.html.md.erb | 50 +++++++-------------
.../implementing_authentication.html.md.erb | 4 +-
.../implementing_authorization.html.md.erb | 4 +-
3 files changed, 20 insertions(+), 38 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/b40485b0/managing/security/enable_security.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/enable_security.html.md.erb b/managing/security/enable_security.html.md.erb
index 441b66c..8f2824c 100644
--- a/managing/security/enable_security.html.md.erb
+++ b/managing/security/enable_security.html.md.erb
@@ -17,42 +17,24 @@ For example:
security-manager = com.example.security.MySecurityManager
```
-## security-enabled-components Property
-
All components of the system invoke the same callbacks.
-Security may be enabled on a component basis with
-the definition of the `security-enabled-components` property.
-Its definition restricts which system components invoke
-the authentication and authorization callbacks.
-The defined values for system components:
-
-- `all`—All components invoke the security callbacks.
-- `server`—Invokes security callbacks upon connection and operation
-requests that a client makes of a server.
-- `cluster`—Invokes security callbacks upon connection and operation
-requests that a server makes as the peer of a locator.
-- `jmx`—Invokes security callbacks upon connection and operation
-requests that components communicating with a JMX manager make of a locator.
+Here are descriptions of the components and the connections that they
+make with the system.
+
+- A client connects with a server and makes operation requests
+of that server. The callbacks invoked are those defined by the
+`SecurityManager` interface for that server.
+- A server connects with a locator, invoking the `authenticate` callback
+defined for that locator.
+- Components communicating with a locator's JMX manager connect and make
+operation requests of the locator.
+The callbacks invoked are those defined by the
+`SecurityManager` interface for that locator.
Both `gfsh` and `Pulse` use this form of communication.
-- `http`—Invokes security callbacks upon connection and operation
-requests that applications communicating via the REST API make of a server.
-- `gateway`—Invokes security callbacks upon connection and operation
-requests that a gateway sender makes of a locator.
-
-The `security-enabled-components` property defines
-a comma-separated list of components that will
-invoke the `authorize` callback.
-For example,
-
-``` pre
-security-enabled-components = server, cluster jmx
-```
-
-The `all` component value is used by itself, as in the example
-
-``` pre
-security-enabled-components = all
-```
+- Applications communicating via the REST API make of a server
+invoke security callbacks upon connection and operation requests.
+- Requests that a gateway sender makes of a locator
+invoke security callbacks defined for that locator.
## security-post-processor Property
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/b40485b0/managing/security/implementing_authentication.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_authentication.html.md.erb b/managing/security/implementing_authentication.html.md.erb
index 9bbb9d3..c238be9 100644
--- a/managing/security/implementing_authentication.html.md.erb
+++ b/managing/security/implementing_authentication.html.md.erb
@@ -28,9 +28,9 @@ that will connect to the system.
This simplistic algorithm returns the user name as a principal
if the user name and password passed to the `authenticate` method
are a match for one of the stored pairs.
-- Define the `security-manager` and `security-enabled-components` properties.
+- Define the `security-manager` property.
See [Enable Security with Property Definitions](enable_security.html)
-for details about these properties.
+for details about this property.
- Implement the `authenticate` method of the `SecurityManager` interface.
- Define any extra resources that the implemented authentication algorithm
needs in order to make a decision.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/b40485b0/managing/security/implementing_authorization.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_authorization.html.md.erb b/managing/security/implementing_authorization.html.md.erb
index 87b4135..3fd4816 100644
--- a/managing/security/implementing_authorization.html.md.erb
+++ b/managing/security/implementing_authorization.html.md.erb
@@ -239,9 +239,9 @@ which operations.
The algorithm bases its decision
on a look up of the permissions granted to the principal attempting
the operation.
-- Define the `security-manager` and `security-enabled-components` properties.
+- Define the `security-manager` property.
See [Enable Security with Property Definitions](enable_security.html)
-for details about these properties.
+for details about this property.
- Implement the `authorize` method of the `SecurityManager` interface.
- Define any extra resources that the implemented authorization algorithm
needs in order to make a decision.
[45/50] [abbrv] incubator-geode git commit: Fix typo in example query
string [#130865217]
Posted by rv...@apache.org.
Fix typo in example query string [#130865217]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/d6dc0fe6
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/d6dc0fe6
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/d6dc0fe6
Branch: refs/staging/docs-grant1
Commit: d6dc0fe6af22ac8406559302a5c582b2b330bf5e
Parents: 42624de
Author: Dave Barnes <db...@pivotal.io>
Authored: Wed Sep 21 15:24:56 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Wed Sep 21 15:24:56 2016 -0700
----------------------------------------------------------------------
getting_started/querying_quick_reference.html.md.erb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/d6dc0fe6/getting_started/querying_quick_reference.html.md.erb
----------------------------------------------------------------------
diff --git a/getting_started/querying_quick_reference.html.md.erb b/getting_started/querying_quick_reference.html.md.erb
index 727c086..9a06d1f 100644
--- a/getting_started/querying_quick_reference.html.md.erb
+++ b/getting_started/querying_quick_reference.html.md.erb
@@ -112,7 +112,7 @@ SELECT DISTINCT * FROM /exampleRegion p WHERE p.status = 'active'
SELECT p.ID, p.status FROM /exampleRegion p WHERE p.ID > 0
```
-**Using the NOT Operator**.
+**Using the NOT Operator**
See [Operators](../developing/query_additional/operators.html#operators) for a complete list of supported operators.
@@ -121,7 +121,7 @@ SELECT DISTINCT * FROM /exampleRegion WHERE NOT (status = 'active') AND ID = 2
```
``` pre
-SELECT * FROM /exampleRegion WHERE NOT (ID IN SET(1,2)
+SELECT * FROM /exampleRegion WHERE NOT (ID IN SET(1,2))
```
**Using the AND and OR Operators**
[40/50] [abbrv] incubator-geode git commit: Update gemfire javadoc
links to geode links [#130062377]
Posted by rv...@apache.org.
Update gemfire javadoc links to geode links [#130062377]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/e2d0ced9
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/e2d0ced9
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/e2d0ced9
Branch: refs/staging/docs-grant1
Commit: e2d0ced9e50bc5bbe9a1665e7d047d86cfc9488a
Parents: ebfed38
Author: Dave Barnes <db...@pivotal.io>
Authored: Tue Sep 20 13:30:07 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Tue Sep 20 13:30:07 2016 -0700
----------------------------------------------------------------------
.../extending_the_autoserializer.html.md.erb | 2 +-
.../data_serialization/gemfire_data_serialization.html.md.erb | 2 +-
.../events/configuring_gateway_concurrency_levels.html.md.erb | 2 +-
.../events/implementing_write_behind_event_handler.html.md.erb | 4 ++--
developing/function_exec/function_execution.html.md.erb | 2 +-
.../query_additional/using_query_bind_parameters.html.md.erb | 2 +-
developing/query_index/maintaining_indexes.html.md.erb | 2 +-
developing/query_select/the_select_statement.html.md.erb | 2 +-
.../querying_basics/querying_partitioned_regions.html.md.erb | 6 +++---
developing/querying_basics/running_a_query.html.md.erb | 4 ++--
developing/transactions/working_with_transactions.html.md.erb | 2 +-
getting_started/querying_quick_reference.html.md.erb | 4 ++--
managing/security/authentication_examples.html.md.erb | 4 ++--
13 files changed, 19 insertions(+), 19 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/data_serialization/extending_the_autoserializer.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/data_serialization/extending_the_autoserializer.html.md.erb b/developing/data_serialization/extending_the_autoserializer.html.md.erb
index 8191787..35cbe66 100644
--- a/developing/data_serialization/extending_the_autoserializer.html.md.erb
+++ b/developing/data_serialization/extending_the_autoserializer.html.md.erb
@@ -27,7 +27,7 @@ You can customize the specific behaviors in `ReflectionBasedAutoSerializer` by o
These methods are only called the first time the `ReflectionBasedAutoSerializer` sees a new class. The results will be remembered and used the next time the same class is seen.
-For details on these methods and their default behaviors, see the JavaDocs on [ReflectionBasedAutoSerializer](/releases/latest/javadoc/com/gemstone/gemfire/pdx/ReflectionBasedAutoSerializer.html) for details.
+For details on these methods and their default behaviors, see the JavaDocs on [ReflectionBasedAutoSerializer](/releases/latest/javadoc/org/apache/geode/pdx/ReflectionBasedAutoSerializer.html) for details.
## <a id="concept_9E020566EE794A81A48A90BA798EC279__section_7C4CC39FD82A48A9B5F8376522078192" class="no-quick-link"></a>Example of Optimizing Autoserialization of BigInteger and BigDecimal Types
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/data_serialization/gemfire_data_serialization.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/data_serialization/gemfire_data_serialization.html.md.erb b/developing/data_serialization/gemfire_data_serialization.html.md.erb
index d3e201b..58aeb7e 100644
--- a/developing/data_serialization/gemfire_data_serialization.html.md.erb
+++ b/developing/data_serialization/gemfire_data_serialization.html.md.erb
@@ -32,4 +32,4 @@ In addition to speeding standard object serialization, you can use the `DataSeri
You can also use `DataSerializer` to serialize domain objects. It serializes data in the same way as `DataSerializable` but allows you to serialize classes without modifying the domain class code.
-See the JavaDocs on [DataSerializable](/releases/latest/javadoc/com/gemstone/gemfire/DataSerializable.html) and [DataSerializer](/releases/latest/javadoc/com/gemstone/gemfire/DataSerializer.html) for more information.
+See the JavaDocs on [DataSerializable](/releases/latest/javadoc/org/apache/geode/DataSerializable.html) and [DataSerializer](/releases/latest/javadoc/org/apache/geode/DataSerializer.html) for more information.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/events/configuring_gateway_concurrency_levels.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/events/configuring_gateway_concurrency_levels.html.md.erb b/developing/events/configuring_gateway_concurrency_levels.html.md.erb
index 8d03cc1..5d001c3 100644
--- a/developing/events/configuring_gateway_concurrency_levels.html.md.erb
+++ b/developing/events/configuring_gateway_concurrency_levels.html.md.erb
@@ -33,7 +33,7 @@ When using multiple `dispatcher-threads` (greater than 1) with a serial event qu
- **key (default)**. All updates to the same key are distributed in order. Geode preserves key ordering by placing all updates to the same key in the same dispatcher thread queue. You typically use key ordering when updates to entries have no relationship to each other, such as for an application that uses a single feeder to distribute stock updates to several other systems.
- **thread**. All region updates from a given thread are distributed in order. Geode preserves thread ordering by placing all region updates from the same thread into the same dispatcher thread queue. In general, use thread ordering when updates to one region entry affect updates to another region entry.
-- **partition**. All region events that share the same partitioning key are distributed in order. Specify partition ordering when applications use a [PartitionResolver](/releases/latest/javadoc/com/gemstone/gemfire/cache/PartitionResolver.html) to implement [custom partitioning](../partitioned_regions/using_custom_partition_resolvers.html). With partition ordering, all entries that share the same "partitioning key" (RoutingObject) are placed into the same dispatcher thread queue.
+- **partition**. All region events that share the same partitioning key are distributed in order. Specify partition ordering when applications use a [PartitionResolver](/releases/latest/javadoc/org/apache/geode/cache/PartitionResolver.html) to implement [custom partitioning](../partitioned_regions/using_custom_partition_resolvers.html). With partition ordering, all entries that share the same "partitioning key" (RoutingObject) are placed into the same dispatcher thread queue.
You cannot configure the `order-policy` for a parallel event queue, because parallel queues cannot preserve event ordering for regions. Only the ordering of events for a given partition (or in a given queue of a distributed region) can be preserved.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/events/implementing_write_behind_event_handler.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/events/implementing_write_behind_event_handler.html.md.erb b/developing/events/implementing_write_behind_event_handler.html.md.erb
index 2fcbb13..908b0f5 100644
--- a/developing/events/implementing_write_behind_event_handler.html.md.erb
+++ b/developing/events/implementing_write_behind_event_handler.html.md.erb
@@ -77,7 +77,7 @@ class MyAsyncEventListener implements AsyncEventListener {
## <a id="implementing_write_behind_cache_event_handling__section_AB80262CFB6D4867B52A5D6D880A5294" class="no-quick-link"></a>Processing AsyncEvents
-Use the [AsyncEventListener.processEvents](/releases/latest/javadoc/com/gemstone/gemfire/cache/asyncqueue/AsyncEventListener.html) method to process AsyncEvents. This method is called asynchronously when events are queued to be processed. The size of the list reflects the number of batch events where batch size is defined in the AsyncEventQueueFactory. The `processEvents` method returns a boolean; true if the AsyncEvents are processed correctly, and false if any events fail processing. As long as `processEvents` returns false, Geode continues to re-try processing the events.
+Use the [AsyncEventListener.processEvents](/releases/latest/javadoc/org/apache/geode/cache/asyncqueue/AsyncEventListener.html) method to process AsyncEvents. This method is called asynchronously when events are queued to be processed. The size of the list reflects the number of batch events where batch size is defined in the AsyncEventQueueFactory. The `processEvents` method returns a boolean; true if the AsyncEvents are processed correctly, and false if any events fail processing. As long as `processEvents` returns false, Geode continues to re-try processing the events.
You can use the `getDeserializedValue` method to obtain cache values for entries that have been updated or created. Since the `getDeserializedValue` method will return a null value for destroyed entries, you should use the `getKey` method to obtain references to cache objects that have been destroyed. Here's an example of processing AsyncEvents:
@@ -217,7 +217,7 @@ To configure a write-behind cache listener, you first configure an asynchronous
mutator.addAsyncEventQueueId("sampleQueue");
```
- See the [Geode API documentation](/releases/latest/javadoc/com/gemstone/gemfire/cache/AttributesMutator.html) for more information.
+ See the [Geode API documentation](/releases/latest/javadoc/org/apache/geode/cache/AttributesMutator.html) for more information.
4. Optionally configure persistence and conflation for the queue.
**Note:**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/function_exec/function_execution.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/function_exec/function_execution.html.md.erb b/developing/function_exec/function_execution.html.md.erb
index a881afd..70fb1a3 100644
--- a/developing/function_exec/function_execution.html.md.erb
+++ b/developing/function_exec/function_execution.html.md.erb
@@ -40,7 +40,7 @@ Code the methods you need for the function. These steps do not have to be done i
**Note:**
When you use `PartitionRegionHelper.getLocalDataForContext`, `putIfAbsent` may not return expected results if you are working on local data set instead of the region.
- 4. To propagate an error condition or exception back to the caller of the function, throw a FunctionException from the `execute` method. Geode transmits the exception back to the caller as if it had been thrown on the calling side. See the Java API documentation for [FunctionException](/releases/latest/javadoc/com/gemstone/gemfire/cache/execute/FunctionException.html) for more information.
+ 4. To propagate an error condition or exception back to the caller of the function, throw a FunctionException from the `execute` method. Geode transmits the exception back to the caller as if it had been thrown on the calling side. See the Java API documentation for [FunctionException](/releases/latest/javadoc/org/apache/geode/cache/execute/FunctionException.html) for more information.
Example function code:
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/query_additional/using_query_bind_parameters.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/query_additional/using_query_bind_parameters.html.md.erb b/developing/query_additional/using_query_bind_parameters.html.md.erb
index bd68471..cf9dcea 100644
--- a/developing/query_additional/using_query_bind_parameters.html.md.erb
+++ b/developing/query_additional/using_query_bind_parameters.html.md.erb
@@ -10,7 +10,7 @@ The use of query bind parameters is now supported in Client-to-Server queries.
The query parameters are identified by a dollar sign, $, followed by a digit that represents the parameter's position in the parameter array passed to the execute method. Counting begins at 1, so $1 references the first bound attribute, $2 the second attribute, and so on.
-The Query interface provides an overloaded execute method that accepts parameters inside an Object array. See the [Query.execute](/releases/latest/javadoc/com/gemstone/gemfire/cache/query/Query.html) JavaDocs for more details.
+The Query interface provides an overloaded execute method that accepts parameters inside an Object array. See the [Query.execute](/releases/latest/javadoc/org/apache/geode/cache/query/Query.html) JavaDocs for more details.
The 0th element of the Object array is used for the first query parameter, and so on. If the parameter count or parameter types do not match the query specification, the execute method throws an exception. Specifically, if you pass in the wrong number of parameters, the method call throws a `QueryParameterCountInvalidException`. If a parameter object type is not compatible with what is expected, the method call throws a `TypeMismatchException`.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/query_index/maintaining_indexes.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/query_index/maintaining_indexes.html.md.erb b/developing/query_index/maintaining_indexes.html.md.erb
index 18ff97e..ae8c29b 100644
--- a/developing/query_index/maintaining_indexes.html.md.erb
+++ b/developing/query_index/maintaining_indexes.html.md.erb
@@ -8,7 +8,7 @@ Indexes are automatically kept current with the region data they reference. The
Asynchronous index maintenance batches up multiple updates to the same region key. The default mode is synchronous, since this provides the greatest consistency with region data.
-See [RegionFactory.setIndexMaintenanceSynchronous](/releases/latest/javadoc/com/gemstone/gemfire/cache/RegionFactory.html).
+See [RegionFactory.setIndexMaintenanceSynchronous](/releases/latest/javadoc/org/apache/geode/cache/RegionFactory.html).
This declarative index creation sets the maintenance mode to asynchronous:
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/query_select/the_select_statement.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/query_select/the_select_statement.html.md.erb b/developing/query_select/the_select_statement.html.md.erb
index 36726bc..04d14df 100644
--- a/developing/query_select/the_select_statement.html.md.erb
+++ b/developing/query_select/the_select_statement.html.md.erb
@@ -44,7 +44,7 @@ TYPE Position WHERE portfolio.status = 'active'
## <a id="concept_85AE7D6B1E2941ED8BD2A8310A81753E__section_1B7762EC686A4808B1D12E8851954E82" class="no-quick-link"></a>SELECT Statement Results
-The result of a SELECT statement is either UNDEFINED or is a Collection that implements the [SelectResults](/releases/latest/javadoc/com/gemstone/gemfire/cache/query/SelectResults.html) interface.
+The result of a SELECT statement is either UNDEFINED or is a Collection that implements the [SelectResults](/releases/latest/javadoc/org/apache/geode/cache/query/SelectResults.html) interface.
The SelectResults returned from the SELECT statement is either:
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/querying_basics/querying_partitioned_regions.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/querying_basics/querying_partitioned_regions.html.md.erb b/developing/querying_basics/querying_partitioned_regions.html.md.erb
index aa811ce..14e7f09 100644
--- a/developing/querying_basics/querying_partitioned_regions.html.md.erb
+++ b/developing/querying_basics/querying_partitioned_regions.html.md.erb
@@ -7,9 +7,9 @@ Geode allows you to manage and store large amounts of data across distributed no
<a id="querying_partitioned_regions__section_4C603563DEDC4303818FB8F894470457"></a>
The following list summarizes the querying functionality supported by Geode for partitioned regions:
-- **Ability to target specific nodes in a query**. If you know that a specific bucket contains the data that you want to query, you can use a function to ensure that your query only runs the specific node that holds the data. This can greatly improve query efficiency. The ability to query data on a specific node is only available if you are using functions and if the function is executed on one single region. In order to do this, you need to use `Query.execute(RegionFunctionContext context)`. See the [Java API](/releases/latest/javadoc/com/gemstone/gemfire/cache/query/Query.html) and [Querying a Partitioned Region on a Single Node](../query_additional/query_on_a_single_node.html#concept_30B18A6507534993BD55C2C9E0544A97) for more details.
-- **Ability to optimize partitioned region query performance using key indexes**. You can improve query performance on data that is partitioned by key or a field value by creating a key index and then executing the query using use `Query.execute(RegionFunctionContext context)` with the key or field value used as filter. See the [Java API](/releases/latest/javadoc/com/gemstone/gemfire/cache/query/Query.html) and [Optimizing Queries on Data Partitioned by a Key or Field Value](../query_additional/partitioned_region_key_or_field_value.html#concept_3010014DFBC9479783B2B45982014454) for more details.
-- **Ability to perform equi-join queries between partitioned regions and between partitioned regions and replicated regions**. Join queries between partitioned region and between partitioned regions and replicated regions are supported through the function service. In order to perform equi-join operations on partitioned regions or partitioned regions and replicated regions, the partitioned regions must be colocated, and you need to use the need to use `Query.execute(RegionFunctionContext context)`. See the [Java API](/releases/latest/javadoc/com/gemstone/gemfire/cache/query/Query.html) and [Performing an Equi-Join Query on Partitioned Regions](../partitioned_regions/join_query_partitioned_regions.html#concept_B930D276F49541F282A2CFE639F107DD) for more details.
+- **Ability to target specific nodes in a query**. If you know that a specific bucket contains the data that you want to query, you can use a function to ensure that your query only runs the specific node that holds the data. This can greatly improve query efficiency. The ability to query data on a specific node is only available if you are using functions and if the function is executed on one single region. In order to do this, you need to use `Query.execute(RegionFunctionContext context)`. See the [Java API](/releases/latest/javadoc/org/apache/geode/cache/query/Query.html) and [Querying a Partitioned Region on a Single Node](../query_additional/query_on_a_single_node.html#concept_30B18A6507534993BD55C2C9E0544A97) for more details.
+- **Ability to optimize partitioned region query performance using key indexes**. You can improve query performance on data that is partitioned by key or a field value by creating a key index and then executing the query using use `Query.execute(RegionFunctionContext context)` with the key or field value used as filter. See the [Java API](/releases/latest/javadoc/org/apache/geode/cache/query/Query.html) and [Optimizing Queries on Data Partitioned by a Key or Field Value](../query_additional/partitioned_region_key_or_field_value.html#concept_3010014DFBC9479783B2B45982014454) for more details.
+- **Ability to perform equi-join queries between partitioned regions and between partitioned regions and replicated regions**. Join queries between partitioned region and between partitioned regions and replicated regions are supported through the function service. In order to perform equi-join operations on partitioned regions or partitioned regions and replicated regions, the partitioned regions must be colocated, and you need to use the need to use `Query.execute(RegionFunctionContext context)`. See the [Java API](/releases/latest/javadoc/org/apache/geode/cache/query/Query.html) and [Performing an Equi-Join Query on Partitioned Regions](../partitioned_regions/join_query_partitioned_regions.html#concept_B930D276F49541F282A2CFE639F107DD) for more details.
- **[Using ORDER BY on Partitioned Regions](../../developing/query_additional/order_by_on_partitioned_regions.html)**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/querying_basics/running_a_query.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/querying_basics/running_a_query.html.md.erb b/developing/querying_basics/running_a_query.html.md.erb
index c17dbed..83b9d1d 100644
--- a/developing/querying_basics/running_a_query.html.md.erb
+++ b/developing/querying_basics/running_a_query.html.md.erb
@@ -61,8 +61,8 @@ To perform a client to server query, use `org.apache.geode.cache.client.Pool.get
Refer to the following JavaDocs for specific APIs:
-- [Query package](/releases/latest/javadoc/com/gemstone/gemfire/cache/query/package-summary.html)
-- [QueryService](/releases/latest/javadoc/com/gemstone/gemfire/cache/query/QueryService.html)
+- [Query package](/releases/latest/javadoc/org/apache/geode/cache/query/package-summary.html)
+- [QueryService](/releases/latest/javadoc/org/apache/geode/cache/query/QueryService.html)
**Note:**
You can also perform queries using the gfsh `query` command. See [query](../../tools_modules/gfsh/command-pages/query.html).
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/developing/transactions/working_with_transactions.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/transactions/working_with_transactions.html.md.erb b/developing/transactions/working_with_transactions.html.md.erb
index ef29bdb..6b30c66 100644
--- a/developing/transactions/working_with_transactions.html.md.erb
+++ b/developing/transactions/working_with_transactions.html.md.erb
@@ -164,7 +164,7 @@ You can also use transaction plug-in event handlers when running JTA global tran
When you commit a transaction, if a transaction writer is installed in the cache where the data updates were performed, it is called. The writer can do whatever work you need, including aborting the transaction.
-The transaction writer is the last place that an application can rollback a transaction. If the transaction writer throws any exception, the transaction is rolled back. For example, you might use a transaction writer to update a backend data source before the Geode cache transaction completes the commit. If the backend data source update fails, the transaction writer implementation can throw a [TransactionWriterException](/releases/latest/javadoc/com/gemstone/gemfire/cache/TransactionWriterException.html) to veto the transaction.
+The transaction writer is the last place that an application can rollback a transaction. If the transaction writer throws any exception, the transaction is rolled back. For example, you might use a transaction writer to update a backend data source before the Geode cache transaction completes the commit. If the backend data source update fails, the transaction writer implementation can throw a [TransactionWriterException](/releases/latest/javadoc/org/apache/geode/cache/TransactionWriterException.html) to veto the transaction.
A typical usage scenario would be to use the transaction writer to prepare the commit on the external database. Then in a transaction listener, you can apply the commit on the database.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/getting_started/querying_quick_reference.html.md.erb
----------------------------------------------------------------------
diff --git a/getting_started/querying_quick_reference.html.md.erb b/getting_started/querying_quick_reference.html.md.erb
index a4d051d..727c086 100644
--- a/getting_started/querying_quick_reference.html.md.erb
+++ b/getting_started/querying_quick_reference.html.md.erb
@@ -490,9 +490,9 @@ ELEMENT(SELECT DISTINCT * FROM /exampleRegion WHERE id = 'XYZ-1').status = 'acti
## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_5383407F9D004D4EB4E695252EBA1EF0" class="no-quick-link"></a>Which APIs should I use to write my queries?
-If you are querying a Java application\u2019s local cache or querying other members, use [org.apache.geode.cache.Cache.getQueryService](/releases/latest/javadoc/com/gemstone/gemfire/cache/query/QueryService.html).
+If you are querying a Java application\u2019s local cache or querying other members, use [org.apache.geode.cache.Cache.getQueryService](/releases/latest/javadoc/org/apache/geode/cache/query/QueryService.html).
-If you are writing a Java client to server query, use [org.apache.geode.cache.client.Pool.getQueryService](/releases/latest/javadoc/com/gemstone/gemfire/cache/client/Pool.html).
+If you are writing a Java client to server query, use [org.apache.geode.cache.client.Pool.getQueryService](/releases/latest/javadoc/org/apache/geode/cache/client/Pool.html).
If you are writing a native client to server query, use the [.NET API](/releases/latest/net_api/DotNetDocs/Index.html) or the [C++ API](/releases/latest/cpp_api/cppdocs/index.html).
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e2d0ced9/managing/security/authentication_examples.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/authentication_examples.html.md.erb b/managing/security/authentication_examples.html.md.erb
index a923679..2d88a40 100644
--- a/managing/security/authentication_examples.html.md.erb
+++ b/managing/security/authentication_examples.html.md.erb
@@ -8,7 +8,7 @@ The security implementation of every installation is unique, so these examples c
## <a id="authentication_examples__section_33A13D8566284AB999B5263844F61133" class="no-quick-link"></a>Using an LDAP Server for Client and Peer Authentication
-The LDAP sample code is within the Geode source tree in the `geode-core/src/test/java/com/gemstone/gemfire/security/templates/` directory. The implementation is in files `UserPasswordAuthInit.java`, `LdapUserAuthenticator.java`, and `UsernamePrincipal.java`.
+The LDAP sample code is within the Geode source tree in the `geode-core/src/test/java/org/apache/geode/security/templates/` directory. The implementation is in files `UserPasswordAuthInit.java`, `LdapUserAuthenticator.java`, and `UsernamePrincipal.java`.
In the example, a client or joining peer submits its credentials to a server or locator, which in turn submits the credentials to the LDAP server. To be authenticated, the credentials must match one of the valid entries in the LDAP server. If the submitted credentials result in a connection to the LDAP server, then the connection is authenticated. If the connection to the LDAP server fails, an AuthenticationFailedException is sent back and the client or peer connection fails.
@@ -39,7 +39,7 @@ The sample `LdapUserAuthenticator` class implements the `Authenticator` interfac
## <a id="authentication_examples__section_6CF27B7574224218A4BA372EB6664732" class="no-quick-link"></a>Using PKCS for Encrypted Client Authentication
-The PKCS sample code is within the Geode source tree in the `geode-core/src/test/java/com/gemstone/gemfire/security/templates/` directory. The implementation is in files `PKCSAuthInit.java`, `PKCSAuthenticator.java`, and `PKCSPrincipal.java`.
+The PKCS sample code is within the Geode source tree in the `geode-core/src/test/java/org/apache/geode/security/templates/` directory. The implementation is in files `PKCSAuthInit.java`, `PKCSAuthenticator.java`, and `PKCSPrincipal.java`.
With this sample, clients send encrypted authentication credentials to a GemFire cache server when they attempt to connect to the server. The credentials are the alias name and digital signature created using the private key retrieved from the provided keystore. The server uses a corresponding public key to decrypt the credentials. If decryption is successful, the client is authenticated and it connects to the server. An unsuccessful decryption generates an `AuthenticationFailedException` that is sent to the client, and the client connection to the server is closed.
[17/50] [abbrv] incubator-geode git commit: Complete content on
integrated security's post processing [#129628127]
Posted by rv...@apache.org.
Complete content on integrated security's post processing [#129628127]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/914b796e
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/914b796e
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/914b796e
Branch: refs/staging/docs-grant1
Commit: 914b796e431ba8b0ff5ad5ab2e946b8962897b53
Parents: c9f6f0d
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Sep 7 09:03:01 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Sep 7 09:03:01 2016 -0700
----------------------------------------------------------------------
managing/security/post_processing.html.md.erb | 44 ++++++++++++++++++++--
1 file changed, 41 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/914b796e/managing/security/post_processing.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/post_processing.html.md.erb b/managing/security/post_processing.html.md.erb
index 8b04380..2a6dc50 100644
--- a/managing/security/post_processing.html.md.erb
+++ b/managing/security/post_processing.html.md.erb
@@ -2,11 +2,49 @@
title: Post Processing of Region Data
---
-The `PostProcessor` interface allows the definition of a set of callbacks
-that are invoked after operations that get data,
+The `PostProcessor` interface allows the definition of a callback
+that is invoked after any and all client and `gfsh` operations that get data,
but before the data is returned.
-This permits the callback to intervene and modify of the data
+It permits the callback to intervene and modify of the data
that is to be returned.
The callbacks do not modify the region data,
only the data to be returned.
+The `processRegionValue` method is given the principal of the
+operation requester.
+The operation will already have been completed,
+implying that the principal will have been authorized to complete
+the requested operation.
+The post processing can therefore modify the returned data based
+on the identity of the requester (principal).
+
+A use of post processing will be to sanitize or mask out sensitive
+region information,
+while providing the remainder of a region entry unchanged.
+An implementation can alter the entry for some requesters,
+but not other requesters.
+
+The `processRegionValue` method is invoked for these API calls:
+
+- `Region.get`
+- `Region.getAll`
+- `Query.execute`
+- `CqQuery.execute`
+- `CqQuery.executeWithInitialResults`
+- `CqListener.onEvent`
+- for a relevant region event from `CacheListener.afterUpdate` for which
+there is interest registered with `Region.registerInterest`
+
+Care should be taken when designing a system that implements the
+post processing callback.
+It incurs the performance penalty of an extra method invocation
+on every get operation.
+
+## Implement Post Processing
+
+Complete these items to implement post processing.
+
+- Define the `security-post-processor` property.
+See [Enable Security with Property Definitions](enable_security.html)
+for details about this property.
+- Implement the `processRegionValue` method of the `PostProcessor` interface.
[20/50] [abbrv] incubator-geode git commit: Merge remote-tracking
branch 'origin/develop' into feature/IntegratedSecurity
Posted by rv...@apache.org.
Merge remote-tracking branch 'origin/develop' into feature/IntegratedSecurity
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/4ad23a10
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/4ad23a10
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/4ad23a10
Branch: refs/staging/docs-grant1
Commit: 4ad23a107208f0a38fa78def296975d082f24498
Parents: f6d9c2b 27455f0
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Sep 7 17:05:15 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Sep 7 17:05:15 2016 -0700
----------------------------------------------------------------------
.../region_shortcuts_reference.html.md.erb | 20 ++++++-------
.../topics/region_shortcuts_table.html.md.erb | 30 ++++++++++----------
2 files changed, 25 insertions(+), 25 deletions(-)
----------------------------------------------------------------------
[18/50] [abbrv] incubator-geode git commit: Write security features
list of items [#129624161]
Posted by rv...@apache.org.
Write security features list of items [#129624161]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/b37c19f1
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/b37c19f1
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/b37c19f1
Branch: refs/staging/docs-grant1
Commit: b37c19f1435d7f430f868ba5ec491d2168bd6b1c
Parents: 914b796
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Sep 7 10:26:08 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Sep 7 10:26:08 2016 -0700
----------------------------------------------------------------------
managing/security/security_intro.html.md.erb | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/b37c19f1/managing/security/security_intro.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/security_intro.html.md.erb b/managing/security/security_intro.html.md.erb
index 6f37bcd..1ebf105 100644
--- a/managing/security/security_intro.html.md.erb
+++ b/managing/security/security_intro.html.md.erb
@@ -5,14 +5,17 @@ title: Security Features
Encryption, SSL secure communication, authentication, and authorization
features help to secure the distributed system.
-Apache Geode features:
+The features include:
-- **Single interface for all components**. one way to rule them all
-- **System-wide role-based access control**. authorization
+- **A single security interface for all components**. The single
+authentication and authorization mechanism simplifies the security
+implementation.
+It views and interacts with all components in a consistent manner.
+- **System-wide role-based access control**.
+Roles regiment authorized operations requested by the various components.
- **SSL communication**. Allows configuration of connections to be
SSL-based, rather than plain socket connections.
You can enable SSL separately for peer-to-peer, client, JMX, gateway senders and receivers, and HTTP connections.
-- **Post processing of region data**. Filtering of return values for get type ops, to permit things like masking off fields. Allows authorization callbacks to modify or filter data from the server.
-- **Sample implementations**. Authentication and authorization sample implementations.
-
+- **Post processing of region data**. Return values for operations that
+return region values may be altered, permitting the filtering of returned data.
[41/50] [abbrv] incubator-geode git commit: Consolidated two sources,
eliminating GemFire versions in favor of a single Geode version:
Using gfsh to manage a remote cluster and Overview of data serialization.
[#126263243]
Posted by rv...@apache.org.
Consolidated two sources, eliminating GemFire versions in favor of a single Geode version: Using gfsh to manage a remote cluster and Overview of data serialization. [#126263243]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/2bd8128e
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/2bd8128e
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/2bd8128e
Branch: refs/staging/docs-grant1
Commit: 2bd8128ee17d7c76b72e0a4d3f4ae1ce29547034
Parents: e2d0ced
Author: Dave Barnes <db...@pivotal.io>
Authored: Tue Sep 20 15:45:59 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Tue Sep 20 15:45:59 2016 -0700
----------------------------------------------------------------------
configuring/cluster_config/gfsh_remote.html.md.erb | 1 +
.../data_serialization/data_serialization_options.html.md.erb | 4 ++++
2 files changed, 5 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/2bd8128e/configuring/cluster_config/gfsh_remote.html.md.erb
----------------------------------------------------------------------
diff --git a/configuring/cluster_config/gfsh_remote.html.md.erb b/configuring/cluster_config/gfsh_remote.html.md.erb
index 4dc0039..9132e44 100644
--- a/configuring/cluster_config/gfsh_remote.html.md.erb
+++ b/configuring/cluster_config/gfsh_remote.html.md.erb
@@ -39,6 +39,7 @@ To connect `gfsh` using the HTTP protocol to a remote GemFire cluster:
- `start jvisualvm`
- `start locator`
- `start server`
+ - `start vsd`
- `status locator``*`
- `status server``*`
- `stop locator``*`
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/2bd8128e/developing/data_serialization/data_serialization_options.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/data_serialization/data_serialization_options.html.md.erb b/developing/data_serialization/data_serialization_options.html.md.erb
index fce15d6..7402ee7 100644
--- a/developing/data_serialization/data_serialization_options.html.md.erb
+++ b/developing/data_serialization/data_serialization_options.html.md.erb
@@ -15,6 +15,9 @@ All data that Geode moves out of the local cache must be serializable. However,
- Regions that receive events from remote caches
- Regions that provide function arguments and results
+**Note:**
+If you are storing objects with the [HTTP Session Management Modules](../../tools_modules/http_session_mgmt/chapter_overview.html), these objects must be serializable since they are serialized before being stored in the region.
+
To minimize the cost of serialization and deserialization, Geode avoids changing the data format whenever possible. This means your data might be stored in the cache in serialized or deserialized form, depending on how you use it. For example, if a server acts only as a storage location for data distribution between clients, it makes sense to leave the data in serialized form, ready to be transmitted to clients that request it. Partitioned region data is always initially stored in serialized form.
## <a id="data_serialization_options__section_691C2CF5A4E24D599070A7AADEDF2BEC" class="no-quick-link"></a>Data Serialization Options
@@ -36,6 +39,7 @@ Geode Data serialization is about 25% faster than PDX serialization, however usi
| Provides single field access of serialized data, without full deserialization - supported also for OQL querying. | � | X |
| Automatically ported to other languages by Geode | � | X |
| Works with .NET clients. | X | X |
+| Works with C++ clients. | X | X |
| Works with Geode delta propagation. | X | X (See note below.) |
<span class="tablecap">**Table 1.** Serialization Options: Comparison of Features</span>
[33/50] [abbrv] incubator-geode git commit: Correct identification of
tc Server and Tomcat versions for HTTP Session Mgmt module [#129957543]
Posted by rv...@apache.org.
Correct identification of tc Server and Tomcat versions
for HTTP Session Mgmt module [#129957543]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/8efe9fb2
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/8efe9fb2
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/8efe9fb2
Branch: refs/staging/docs-grant1
Commit: 8efe9fb2520a4a802ae19924b85c273630dba45c
Parents: 66a81e8
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Sep 14 09:53:34 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Sep 14 09:53:34 2016 -0700
----------------------------------------------------------------------
tools_modules/http_session_mgmt/quick_start.html.md.erb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/8efe9fb2/tools_modules/http_session_mgmt/quick_start.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/http_session_mgmt/quick_start.html.md.erb b/tools_modules/http_session_mgmt/quick_start.html.md.erb
index 007621a..186f35b 100644
--- a/tools_modules/http_session_mgmt/quick_start.html.md.erb
+++ b/tools_modules/http_session_mgmt/quick_start.html.md.erb
@@ -25,8 +25,8 @@ In this section you download, install, and set up the HTTP Session Management mo
| Supported Application Server | Version | Module | Target Location for Module |
|------------------------------|-----------------------------|----------------------------------------------------------|----------------------------------------------------------------------------------|
| tc Server | 2.9 (Deprecated) | HTTP Session Management Module for Pivotal tc Server | `<tc Server root dir>/templates` |
- | tc Server | 3.0 | HTTP Session Management Module for Pivotal tc Server 3.0 | `<tc Server root dir>/templates` |
- | Tomcat | 7.0 | HTTP Session Management Module for Tomcat | `$CATALINA_HOME` |
+ | tc Server | 3.0 and 3.1 | HTTP Session Management Module for Pivotal tc Server | `<tc Server root dir>/templates` |
+ | Tomcat | 7.0 and 8.0 | HTTP Session Management Module for Tomcat | `$CATALINA_HOME` |
| WebLogic | 11g (10.3.x) | HTTP Session Management Module for AppServers | *any directory* |
| WebSphere | 7, 8 | HTTP Session Management Module for AppServers | *any directory* |
| JBoss | 5, 6, 7 | HTTP Session Management Module for AppServers | *any directory* |
[48/50] [abbrv] incubator-geode git commit: Add empty sections as
placeholders for automated rebalance documentation. [#120394673]
Posted by rv...@apache.org.
Add empty sections as placeholders for automated rebalance
documentation. [#120394673]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/6b8d375a
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/6b8d375a
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/6b8d375a
Branch: refs/staging/docs-grant1
Commit: 6b8d375a62de178a7815cf234d20f58169b7c33b
Parents: 21cdeff
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Sep 28 17:12:38 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Sep 28 17:12:38 2016 -0700
----------------------------------------------------------------------
developing/partitioned_regions/automated_rebalance.html.md.erb | 6 ++++++
developing/partitioned_regions/chapter_overview.html.md.erb | 4 ++++
2 files changed, 10 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6b8d375a/developing/partitioned_regions/automated_rebalance.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/partitioned_regions/automated_rebalance.html.md.erb b/developing/partitioned_regions/automated_rebalance.html.md.erb
new file mode 100644
index 0000000..d134b8c
--- /dev/null
+++ b/developing/partitioned_regions/automated_rebalance.html.md.erb
@@ -0,0 +1,6 @@
+---
+title: Automated Rebalancing
+---
+
+What it is and how it works.
+
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6b8d375a/developing/partitioned_regions/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/partitioned_regions/chapter_overview.html.md.erb b/developing/partitioned_regions/chapter_overview.html.md.erb
index 56e65e1..26579c2 100644
--- a/developing/partitioned_regions/chapter_overview.html.md.erb
+++ b/developing/partitioned_regions/chapter_overview.html.md.erb
@@ -32,6 +32,10 @@ In addition to basic region management, partitioned regions include options for
In a distributed system with minimal contention to the concurrent threads reading or updating from the members, you can use rebalancing to dynamically increase or decrease your data and processing capacity.
+- **[Automated Rebalancing](../../developing/partitioned_regions/automated_rebalance.html)**
+
+ Short description of automated rebalancing.
+
- **[Checking Redundancy in Partitioned Regions](../../developing/partitioned_regions/checking_region_redundancy.html)**
Under some circumstances, it can be important to verify that your partitioned region data is redundant and that upon member restart, redundancy has been recovered properly across partitioned region members.
[23/50] [abbrv] incubator-geode git commit: GEODE-37 Package renaming
[#118023839]
Posted by rv...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/reference/topics/client-cache.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/client-cache.html.md.erb b/reference/topics/client-cache.html.md.erb
index 3ae87e0..8c42c16 100644
--- a/reference/topics/client-cache.html.md.erb
+++ b/reference/topics/client-cache.html.md.erb
@@ -7,7 +7,7 @@ This section documents all `cache.xml` elements that you use to configure Geode
For Geode server configuration, see [<cache> Element Reference](cache_xml.html).
-API: `com.gemstone.gemfire.cache.client.ClientCacheFactory` and `PoolFactory` interfaces.
+API: `org.apache.geode.cache.client.ClientCacheFactory` and `PoolFactory` interfaces.
<a id="cc-client-cache__table_B079C5A320194B3A98AD82DDB67DA43D"></a>
@@ -103,7 +103,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
Use for client caches. Defines a client's server pool used to communicate with servers running in a different distributed system.
-**API:** `com.gemstone.gemfire.cache.client.PoolFactory`
+**API:** `org.apache.geode.cache.client.PoolFactory`
<a id="cc-pool__d93e1237"></a>
@@ -267,7 +267,7 @@ Addresses and ports of the locators to connect to. You can define multiple locat
**Note:**
Provide a locator list or `server` list, but not both.
-**API:** `com.gemstone.gemfire.distributed.LocatorLauncher`
+**API:** `org.apache.geode.distributed.LocatorLauncher`
<a id="cc-locator__d93e1621"></a>
@@ -296,7 +296,7 @@ Provide a server list or `locator` list, but not both.
**Default:**
-**API:** `com.gemstone.gemfire.distributed.ServerLauncher`
+**API:** `org.apache.geode.distributed.ServerLauncher`
<a id="cc-server__d93e1724"></a>
@@ -323,7 +323,7 @@ Defines a pool of one or more disk stores, which can be used by regions, and cli
**Default:** The cache default disk store, named "DEFAULT", is used when disk is used but no disk store is named.
-**API:** `com.gemstone.gemfire.cache.DiskStore`
+**API:** `org.apache.geode.cache.DiskStore`
<a id="cc-disk-store__d93e1818"></a>
@@ -461,7 +461,7 @@ Specifies a region or disk store's disk directory.
Specifies the configuration for the Portable Data eXchange (PDX) method of serialization.
-**API:** `com.gemstone.gemfire.cache.CacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields` and `com.gemstone.gemfire.cache.ClientCacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields`
+**API:** `org.apache.geode.cache.CacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields` and `org.apache.geode.cache.ClientCacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields`
<a id="cc-pdx__d93e2117"></a>
@@ -481,7 +481,7 @@ Specifies the configuration for the Portable Data eXchange (PDX) method of seria
<pdx persistent="true" disk-store-name="myDiskStore">
<pdx-serializer>
<class-name>
- com.gemstone.gemfire.pdx.ReflectionBasedAutoSerializer
+ org.apache.geode.pdx.ReflectionBasedAutoSerializer
</class-name>
<parameter name="classes">
<string>com.company.domain.DomainObject</string>>
@@ -500,7 +500,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
**Default:**
-**API:** `com.gemstone.gemfire.cache.CacheFactory.setPdxSerializer`
+**API:** `org.apache.geode.cache.CacheFactory.setPdxSerializer`
**Example:**
@@ -519,7 +519,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
Specifies a region attributes template that can be named (by `id`) and referenced (by `refid`) later in the `cache.xml` and through the API.
-**API:** `com.gemstone.gemfire.cache.RegionFactory` or `com.gemstone.gemfire.cache.ClientRegionFactory`
+**API:** `org.apache.geode.cache.RegionFactory` or `org.apache.geode.cache.ClientRegionFactory`
<a id="cc-region-attributes__d93e2287"></a>
@@ -857,7 +857,7 @@ Used only with GemFire version 6.x gateway configurations. For GemFire 7.0 confi
</tr>
<tr class="even">
<td>statistics-enabled</td>
-<td>Boolean specifying whether to gather statistics on the region. Must be true to use expiration on the region. Geode provides a standard set of statistics for cached regions and region entries, which give you information for fine-tuning your distributed system. Unlike other Geode statistics, statistics for local and distributed regions are not archived and cannot be charted. They are kept in instances of <code class="ph codeph">com.gemstone.gemfire.cache.CacheStatistics</code> and made available through the region and its entries through the <code class="ph codeph">Region.getStatistics</code> and <code class="ph codeph">Region.Entry.getStatistics</code> methods.
+<td>Boolean specifying whether to gather statistics on the region. Must be true to use expiration on the region. Geode provides a standard set of statistics for cached regions and region entries, which give you information for fine-tuning your distributed system. Unlike other Geode statistics, statistics for local and distributed regions are not archived and cannot be charted. They are kept in instances of <code class="ph codeph">org.apache.geode.cache.CacheStatistics</code> and made available through the region and its entries through the <code class="ph codeph">Region.getStatistics</code> and <code class="ph codeph">Region.Entry.getStatistics</code> methods.
<p><strong>API:</strong> <code class="ph codeph">setStatisticsEnabled</code></p>
<p><strong>Example:</strong></p>
<pre class="pre codeblock language-xml"><code><region-attributes
@@ -913,7 +913,7 @@ Set the constraint in every cache where you create or update the region entries.
**Default:** not set
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setKeyConstraint`
+**API:** `org.apache.geode.cache.RegionFactory.setKeyConstraint`
**Example:**
@@ -934,7 +934,7 @@ Set the constraint in every cache where you create or update the region entries.
**Default:** not set
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setValueConstraint`
+**API:** `org.apache.geode.cache.RegionFactory.setValueConstraint`
**Example:**
@@ -952,7 +952,7 @@ Expiration setting that specifies how long the region can remain in the cache wi
**Default:** not set - no expiration of this type
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setRegionTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setRegionTimeToLive`
**Example:**
@@ -1043,11 +1043,11 @@ Select one of the following expiration actions:
## <a id="cc-custom-expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -1075,7 +1075,7 @@ To ensure reliable read behavior across the partitioned region, use `region-time
**Default:** not set - no expiration of this type
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setRegionIdleTimeout`
+**API:** `org.apache.geode.cache.RegionFactory.setRegionIdleTimeout`
**Example:**
@@ -1165,11 +1165,11 @@ Select one of the following expiration actions:
## <a id="cc-rit-custom-expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -1194,7 +1194,7 @@ Expiration setting that specifies how long the region\u2019s entries can remain in
**Default:** not set - no expiration of this type.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setEntryTimeToLive`
**Example:**
@@ -1285,11 +1285,11 @@ Select one of the following expiration actions:
## <a id="cc-ettl-custom-expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -1315,7 +1315,7 @@ Expiration setting that specifies how long the region\u2019s entries can remain in
**Note:**
To ensure reliable read behavior across the partitioned region, use `entry-time-to-live` for entry expiration instead of this setting.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setEntryIdleTimeout`
+**API:** `org.apache.geode.cache.RegionFactory.setEntryIdleTimeout`
**Example:**
@@ -1407,11 +1407,11 @@ Select one of the following expiration actions:
## <a id="cc-eit-custom-expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -1436,7 +1436,7 @@ An event-handler plug-in that allows you to program for cache misses. At most, o
For partitioned regions, if you want to have a cache loader, install an instance of the cache loader in every data store. Partitioned regions support partitioned loading, where each cache loader loads only the data entries in the local member. If data redundancy is configured, data is loaded only if the local member holds the primary copy.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCacheLoader`
+**API:** `org.apache.geode.cache.RegionFactory.setCacheLoader`
**Example:**
@@ -1452,7 +1452,7 @@ For partitioned regions, if you want to have a cache loader, install an instance
An event-handler plug-in that allows you to receive before-event notification for changes to the region and its entries. It also has the ability to abort events. At most, one cache writer can be defined in each member for the region. A cache writer may be invoked remotely from other members that have the region defined.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCacheWriter`
+**API:** `org.apache.geode.cache.RegionFactory.setCacheWriter`
**Example:**
@@ -1470,7 +1470,7 @@ An event-handler plug-in that receives after-event notification of changes to th
Specify the Java class for the cache listener and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements. See [<class-name> and <parameter>](cache_xml.html#class-name_parameter).
-**API:** `com.gemstone.gemfire.cache.RegionFactory.addCacheListener`
+**API:** `org.apache.geode.cache.RegionFactory.addCacheListener`
**Example:**
@@ -1490,7 +1490,7 @@ Specifies whether and how to control a region\u2019s size. Size is controlled by re
**Default:** Uses the lru-entry-count algorithm.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setEvictionAttributes`
+**API:** `org.apache.geode.cache.RegionFactory.setEvictionAttributes`
**Example:**
@@ -1879,7 +1879,7 @@ Defines a region in the cache. See [<region-attributes>](cache_xml.html#re
**Default:**
-**API:** `com.gemstone.gemfire.cache.RegionFactory` or `com.gemstone.gemfire.cache.ClientRegionFactory`
+**API:** `org.apache.geode.cache.RegionFactory` or `org.apache.geode.cache.ClientRegionFactory`
<a id="cc-region__d93e5829"></a>
@@ -1918,7 +1918,7 @@ See[<region-attributes>](cache_xml.html#region-attributes) for a complete
Specifies a region attributes template that can be named (by `id`) and referenced (by `refid`) later in the `cache.xml` and through the API.
-**API:** `com.gemstone.gemfire.cache.RegionFactory` or `com.gemstone.gemfire.cache.ClientRegionFactory`
+**API:** `org.apache.geode.cache.RegionFactory` or `org.apache.geode.cache.ClientRegionFactory`
<a id="cc-r-region-attributes__d93e2287"></a>
@@ -2256,7 +2256,7 @@ Used only with GemFire version 6.x gateway configurations. For GemFire 7.0 confi
</tr>
<tr class="even">
<td>statistics-enabled</td>
-<td>Boolean specifying whether to gather statistics on the region. Must be true to use expiration on the region. Geode provides a standard set of statistics for cached regions and region entries, which give you information for fine-tuning your distributed system. Unlike other Geode statistics, statistics for local and distributed regions are not archived and cannot be charted. They are kept in instances of <code class="ph codeph">com.gemstone.gemfire.cache.CacheStatistics</code> and made available through the region and its entries through the <code class="ph codeph">Region.getStatistics</code> and <code class="ph codeph">Region.Entry.getStatistics</code> methods.
+<td>Boolean specifying whether to gather statistics on the region. Must be true to use expiration on the region. Geode provides a standard set of statistics for cached regions and region entries, which give you information for fine-tuning your distributed system. Unlike other Geode statistics, statistics for local and distributed regions are not archived and cannot be charted. They are kept in instances of <code class="ph codeph">org.apache.geode.cache.CacheStatistics</code> and made available through the region and its entries through the <code class="ph codeph">Region.getStatistics</code> and <code class="ph codeph">Region.Entry.getStatistics</code> methods.
<p><strong>API:</strong> <code class="ph codeph">setStatisticsEnabled</code></p>
<p><strong>Example:</strong></p>
<pre class="pre codeblock language-xml"><code><region-attributes
@@ -2309,7 +2309,7 @@ Describes an index to be created on a region. The index node, if any, should all
**Default:**
-**API:** `com.gemstone.gemfire.cache.query.QueryService.createIndex, createKeyIndex, createHashIndex`
+**API:** `org.apache.geode.cache.query.QueryService.createIndex, createKeyIndex, createHashIndex`
<a id="cc-index__d93e5943"></a>
@@ -2352,7 +2352,7 @@ An "entry" element describes an entry to be added to a region. Note that if an e
**Default:**
-**API:** `com.gemstone.gemfire.cache.Region.create`, `put`, `get`, `putAll`, `getAll`
+**API:** `org.apache.geode.cache.Region.create`, `put`, `get`, `putAll`, `getAll`
**Example:**
@@ -2403,7 +2403,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<parameter name="cacheserver">
<declarable>
- <class-name>com.gemstone.gemfire.addon.cache.CacheServerInitializer</class-name>
+ <class-name>org.apache.geode.addon.cache.CacheServerInitializer</class-name>
<parameter name="system.property.prefix">
<string>cacheserver</string>
</parameter>
@@ -2446,7 +2446,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<parameter name="cacheserver">
<declarable>
- <class-name>com.gemstone.gemfire.addon.cache.CacheServerInitializer</class-name>
+ <class-name>org.apache.geode.addon.cache.CacheServerInitializer</class-name>
<parameter name="system.property.prefix">
<string>cacheserver</string>
</parameter>
@@ -2460,7 +2460,7 @@ Defines a region in the cache. See [<region-attributes>](cache_xml.html#re
**Default:**
-**API:** `com.gemstone.gemfire.cache.RegionFactory` or `com.gemstone.gemfire.cache.ClientRegionFactory`
+**API:** `org.apache.geode.cache.RegionFactory` or `org.apache.geode.cache.ClientRegionFactory`
<a id="cc-ra-region__d93e5829"></a>
@@ -2520,7 +2520,7 @@ Specify the Java class for the function and its initialization parameters with t
**Default:**
-**API:** `com.gemstone.gemfire.cache.execute.FunctionService`
+**API:** `org.apache.geode.cache.execute.FunctionService`
**Example:**
@@ -2536,7 +2536,7 @@ Specify the Java class for the function and its initialization parameters with t
A memory monitor that tracks cache size as a percentage of total heap or off-heap memory and controls size by restricting access to the cache and prompting eviction of old entries from the cache. For tenured heap, used in conjunction with settings for JVM memory and Java garbage collection. For off-heap memory, used with the off-heap memory manager.
-**API:** `com.gemstone.gemfire.cache.control.ResourceManager`
+**API:** `org.apache.geode.cache.control.ResourceManager`
<a id="cc-resource-manager__d93e6336"></a>
@@ -2622,7 +2622,7 @@ Allows you to configure the DataSerializer for this Geode member. It registers a
Specify the Java class for the `DataSerializer` and its initialization parameters with the `<class-name>` sub-element.
-**API:** You can also register a `DataSerializer` by using the `com.gemstone.gemfire.DataSerializer.register` API. Use the `com.gemstone.gemfire.Instantiator` API to register a `DataSerializable` implementation.
+**API:** You can also register a `DataSerializer` by using the `org.apache.geode.DataSerializer.register` API. Use the `org.apache.geode.Instantiator` API to register a `DataSerializable` implementation.
## <a id="cc-instantiator" class="no-quick-link"></a><instantiator>
@@ -2632,7 +2632,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
**API:** `DataSerializable`
-You can also directly specify `<instantiator>` as a sub-element of `<cache>`. Use the `com.gemstone.gemfire.Instantiator` API to register a `DataSerializable` implementation as the serialization framework for the cache. The following table lists the attribute that can be specified for an `<instantiator>`.
+You can also directly specify `<instantiator>` as a sub-element of `<cache>`. Use the `org.apache.geode.Instantiator` API to register a `DataSerializable` implementation as the serialization framework for the cache. The following table lists the attribute that can be specified for an `<instantiator>`.
<a id="cc-instantiator__d93e6596"></a>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/reference/topics/elements_ref.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/elements_ref.html.md.erb b/reference/topics/elements_ref.html.md.erb
index 3b5620a..9b13fab 100644
--- a/reference/topics/elements_ref.html.md.erb
+++ b/reference/topics/elements_ref.html.md.erb
@@ -40,7 +40,7 @@ The cache.xml file has these requirements:
</client-cache>
```
-- Any class name specified in the file **must have a public zero-argument constructor** and must implement the `com.gemstone.gemfire.cache.Declarable` interface. Parameters declared in the XML for the class are passed to the class init method.
+- Any class name specified in the file **must have a public zero-argument constructor** and must implement the `org.apache.geode.cache.Declarable` interface. Parameters declared in the XML for the class are passed to the class init method.
## <a id="topic_7B1CABCAD056499AA57AF3CFDBF8ABE3__section_5DBA12F9FC08406AAD5557E13A3DEDF2" class="no-quick-link"></a>Variables in cache.xml
@@ -79,7 +79,7 @@ To configure cache servers, clients, and WAN topologies, see the following secti
- [<region>](cache_xml.html#region)
- [<region-attributes>](cache_xml.html#region-attributes)
- You can set the same server configuration properties using the <span class="keyword apiname">`com.gemstone.gemfire.cache.server.CacheServer`</span> and <span class="keyword apiname">`com.gemstone.gemfire.cache.Cache`</span> interfaces. For detailed information, see the online Java API documentation.
+ You can set the same server configuration properties using the <span class="keyword apiname">`org.apache.geode.cache.server.CacheServer`</span> and <span class="keyword apiname">`org.apache.geode.cache.Cache`</span> interfaces. For detailed information, see the online Java API documentation.
- Client Configuration
@@ -87,7 +87,7 @@ To configure cache servers, clients, and WAN topologies, see the following secti
- [<pool>](client-cache.html#cc-pool)
- [<region>](client-cache.html#cc-region)
- You can set the same client configuration properties using the <span class="keyword apiname">`com.gemstone.gemfire.cache.clientClientCache`</span> and <span class="keyword apiname">`Pool`</span> interfaces. For detailed information, see the online Java API documentation.
+ You can set the same client configuration properties using the <span class="keyword apiname">`org.apache.geode.cache.clientClientCache`</span> and <span class="keyword apiname">`Pool`</span> interfaces. For detailed information, see the online Java API documentation.
- Multi-site (WAN) Configuration and Asynchronous Event Queue Configuration
@@ -95,6 +95,6 @@ To configure cache servers, clients, and WAN topologies, see the following secti
- [<gateway-receiver>](../../reference/topics/gfe_cache_xml.html#gateway-receiver)
- [<async-event-queue>](../../reference/topics/gfe_cache_xml.html#id_zrr_scq_rr)
- The gateway sender and receiver APIs in <span class="keyword apiname">`com.gemstone.gemfire.cache.util`</span> provide corresponding getter and setter methods for these attributes.
+ The gateway sender and receiver APIs in <span class="keyword apiname">`org.apache.geode.cache.util`</span> provide corresponding getter and setter methods for these attributes.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/reference/topics/gfe_cache_xml.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/gfe_cache_xml.html.md.erb b/reference/topics/gfe_cache_xml.html.md.erb
index 2f37ea2..fbe289d 100644
--- a/reference/topics/gfe_cache_xml.html.md.erb
+++ b/reference/topics/gfe_cache_xml.html.md.erb
@@ -6,7 +6,7 @@ This section documents the `cache.xml` sub-elements used for Geode server config
For Geode client configuration, see [<client-cache> Element Reference](client-cache.html#cc-client-cache).
-**API**:`com.gemstone.gemfire.cache.CacheFactory`
+**API**:`org.apache.geode.cache.CacheFactory`
<a id="id_zn4_qbq_rr__d2116e40"></a>
@@ -124,7 +124,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
## <a id="id_sqg_3cq_rr" class="no-quick-link"></a><dynamic-region-factory>
-The `<dynamic-region-factory>` element configures a dynamic region factory for this cache. You can use this element to dynamically create regions in your application code. Use the <span class="keyword apiname">createDynamicRegion()</span> method of the <span class="keyword apiname">com.gemstone.gemfire.cache.DynamicRegionFactory</span> class in your Java code to dynamically create regions.
+The `<dynamic-region-factory>` element configures a dynamic region factory for this cache. You can use this element to dynamically create regions in your application code. Use the <span class="keyword apiname">createDynamicRegion()</span> method of the <span class="keyword apiname">org.apache.geode.cache.DynamicRegionFactory</span> class in your Java code to dynamically create regions.
**Note:**
You can not use this element to dynamically create *partitioned* regions.
@@ -135,7 +135,7 @@ The optional `<disk-dir>` sub-element specifies the directory to store the persi
Set the `pool-name` attribute to set the name of the connection pool used by client applications in a client/server cache configuration. Do not specify the `pool-name` attribute in servers or peers.
-**API:** `com.gemstone.gemfire.cache.DynamicRegionFactory`
+**API:** `org.apache.geode.cache.DynamicRegionFactory`
<a id="id_sqg_3cq_rr__d2116e313"></a>
@@ -342,14 +342,14 @@ When distributing region events from the local queue, multiple dispatcher thread
parallel="true"
remote-distributed-system-id="1">
<gateway-event-filter>
- <class-name>com.gemstone.gemfire.util.SampleEventFilter</class-name>
+ <class-name>org.apache.geode.util.SampleEventFilter</class-name>
<parameter
name="param1">
<string>"value1"</string>
</parameter>
</gateway-event-filter>
<gateway-transport-filter>
- <class-name>com.gemstone.gemfire.util.SampleTransportFilter</class-name>
+ <class-name>org.apache.geode.util.SampleTransportFilter</class-name>
<parameter
name="param1">
<string>"value1"</string>
@@ -370,7 +370,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<gateway-event-filter>
- <class-name>com.gemstone.gemfire.util.SampleEventFilter</class-name>
+ <class-name>org.apache.geode.util.SampleEventFilter</class-name>
<parameter name="param1">
<string>"value1"</string>
</parameter>
@@ -387,7 +387,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<gateway-event-substitution-filter>
- <class-name>com.gemstone.gemfire.util.SampleEventSubstitutionFilter</class-name>
+ <class-name>org.apache.geode.util.SampleEventSubstitutionFilter</class-name>
<parameter name="param1">
<string>"value1"</string>
</parameter>
@@ -404,7 +404,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<gateway-transport-filter>
- <class-name>com.gemstone.gemfire.util.SampleTransportFilter</class-name>
+ <class-name>org.apache.geode.util.SampleTransportFilter</class-name>
<parameter
name="param1">
<string>"value1"</string>
@@ -483,7 +483,7 @@ Configures a gateway receiver to receive and apply region events that were distr
<cache>
<gateway-receiver start-port="1530" end-port="1551">
<gateway-transport-filter>>
- <class-name>com.gemstone.gemfire.util.SampleTransportFilter</class-name>
+ <class-name>org.apache.geode.util.SampleTransportFilter</class-name>
<parameter
name="param1">
<string>"value1"</string>
@@ -503,7 +503,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<gateway-transport-filter>
- <class-name>com.gemstone.gemfire.util.SampleTransportFilter</class-name>
+ <class-name>org.apache.geode.util.SampleTransportFilter</class-name>
<parameter
name="param1">
<string>"value1"</string>
@@ -517,7 +517,7 @@ An event-handler plug-in that is called in order to determine whether a potentia
Specify the Java class for the gateway conflict resolver plug-in and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements. See [<class-name> and <parameter>](#class-name_parameter).
-**API:** `com.gemstone.gemfire.cache.util.GatewayConflictResolver`
+**API:** `org.apache.geode.cache.util.GatewayConflictResolver`
**Example:**
@@ -533,7 +533,7 @@ Specify the Java class for the gateway conflict resolver plug-in and its initial
Configures a queue for sending region events to an AsyncEventListener implementation (for example, for write-behind event handling).
-**API:** `com.gemstone.gemfire.cache.asyncqueue.AsyncEventQueue`
+**API:** `org.apache.geode.cache.asyncqueue.AsyncEventQueue`
<a id="id_zrr_scq_rr__d2116e424"></a>
@@ -654,7 +654,7 @@ An AsyncEventListener receives callbacks for events that change region data. You
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements. See [<class-name> and <parameter>](cache_xml.html#class-name_parameter).
-**API:** `com.gemstone.gemfire.cache.asyncqueue.AsyncEventListener`
+**API:** `org.apache.geode.cache.asyncqueue.AsyncEventListener`
**Example:**
@@ -679,9 +679,9 @@ Specify the Java class and its initialization parameters with the `<class-name>`
Configures the cache to serve region data to clients in a client/server caching system. This element indicates the port the server listens on for client communication.
-The `cacheserver` process uses only `cache.xml` configuration. For application servers, you can set the same configuration properties using the `com.gemstone.gemfire.cache.server.CacheServer` and `com.gemstone.gemfire.cache.Cache` interfaces. For detailed information, see the online Java API documentation.
+The `cacheserver` process uses only `cache.xml` configuration. For application servers, you can set the same configuration properties using the `org.apache.geode.cache.server.CacheServer` and `org.apache.geode.cache.Cache` interfaces. For detailed information, see the online Java API documentation.
-**API:** `com.gemstone.gemfire.cache.server.CacheServer`
+**API:** `org.apache.geode.cache.server.CacheServer`
<a id="id_j5l_xcq_rr__d2116e795"></a>
@@ -832,7 +832,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
**Default:** If this is not defined, the default Geode load probe is used.
-**API:** `com.gemstone.gemfire.cache.server.setLoadProbe`
+**API:** `org.apache.geode.cache.server.setLoadProbe`
**Example:**
@@ -848,7 +848,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
Use for client caches. Defines a client's server pool used to communicate with servers running in a different distributed system.
-**API:** `com.gemstone.gemfire.cache.client.PoolFactory`
+**API:** `org.apache.geode.cache.client.PoolFactory`
<a id="id_jbr_kdq_rr__d2116e1237"></a>
@@ -1012,7 +1012,7 @@ Addresses and ports of the locators to connect to. You can define multiple locat
**Note:**
Provide a locator list or `server` list, but not both.
-**API:** `com.gemstone.gemfire.distributed.LocatorLauncher`
+**API:** `org.apache.geode.distributed.LocatorLauncher`
<a id="id_fsd_ldq_rr__d2116e1621"></a>
@@ -1041,7 +1041,7 @@ Provide a server list or `locator` list, but not both.
**Default:**
-**API:** `com.gemstone.gemfire.distributed.ServerLauncher`
+**API:** `org.apache.geode.distributed.ServerLauncher`
<a id="id_ds3_ndq_rr__d2116e1724"></a>
@@ -1068,7 +1068,7 @@ Defines a pool of one or more disk stores, which can be used by regions, and cli
**Default:** The cache default disk store, named "DEFAULT", is used when disk is used but no disk store is named.
-**API:** `com.gemstone.gemfire.cache.DiskStore`
+**API:** `org.apache.geode.cache.DiskStore`
<a id="id_q21_5dq_rr__d2116e1818"></a>
@@ -1206,7 +1206,7 @@ Specifies a region or disk store's disk directory.
Specifies the configuration for the Portable Data eXchange (PDX) method of serialization.
-**API:** `com.gemstone.gemfire.cache.CacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields` and `com.gemstone.gemfire.cache.ClientCacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields`
+**API:** `org.apache.geode.cache.CacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields` and `org.apache.geode.cache.ClientCacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields`
<a id="id_vvt_vdq_rr__d2116e2117"></a>
@@ -1226,7 +1226,7 @@ Specifies the configuration for the Portable Data eXchange (PDX) method of seria
<pdx persistent="true" disk-store-name="myDiskStore">
<pdx-serializer>
<class-name>
- com.gemstone.gemfire.pdx.ReflectionBasedAutoSerializer
+ org.apache.geode.pdx.ReflectionBasedAutoSerializer
</class-name>
<parameter name="classes">
<string>com.company.domain.DomainObject</string>>
@@ -1245,7 +1245,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
**Default:**
-**API:** `com.gemstone.gemfire.cache.CacheFactory.setPdxSerializer`
+**API:** `org.apache.geode.cache.CacheFactory.setPdxSerializer`
**Example:**
@@ -1264,7 +1264,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
Specifies a region attributes template that can be named (by `id`) and referenced (by `refid`) later in the `cache.xml` and through the API.
-**API:** `com.gemstone.gemfire.cache.RegionFactory` or `com.gemstone.gemfire.cache.ClientRegionFactory`
+**API:** `org.apache.geode.cache.RegionFactory` or `org.apache.geode.cache.ClientRegionFactory`
<a id="id_p1s_ydq_rr__d2116e2287"></a>
@@ -1602,7 +1602,7 @@ Used only with GemFire version 6.x gateway configurations. For GemFire 7.0 confi
</tr>
<tr class="even">
<td>statistics-enabled</td>
-<td>Boolean specifying whether to gather statistics on the region. Must be true to use expiration on the region. Geode provides a standard set of statistics for cached regions and region entries, which give you information for fine-tuning your distributed system. Unlike other Geode statistics, statistics for local and distributed regions are not archived and cannot be charted. They are kept in instances of <code class="ph codeph">com.gemstone.gemfire.cache.CacheStatistics</code> and made available through the region and its entries through the <code class="ph codeph">Region.getStatistics</code> and <code class="ph codeph">Region.Entry.getStatistics</code> methods.
+<td>Boolean specifying whether to gather statistics on the region. Must be true to use expiration on the region. Geode provides a standard set of statistics for cached regions and region entries, which give you information for fine-tuning your distributed system. Unlike other Geode statistics, statistics for local and distributed regions are not archived and cannot be charted. They are kept in instances of <code class="ph codeph">org.apache.geode.cache.CacheStatistics</code> and made available through the region and its entries through the <code class="ph codeph">Region.getStatistics</code> and <code class="ph codeph">Region.Entry.getStatistics</code> methods.
<p><strong>API:</strong> <code class="ph codeph">setStatisticsEnabled</code></p>
<p><strong>Example:</strong></p>
<pre class="pre codeblock language-xml"><code><region-attributes
@@ -1658,7 +1658,7 @@ Set the constraint in every cache where you create or update the region entries.
**Default:** not set
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setKeyConstraint`
+**API:** `org.apache.geode.cache.RegionFactory.setKeyConstraint`
**Example:**
@@ -1679,7 +1679,7 @@ Set the constraint in every cache where you create or update the region entries.
**Default:** not set
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setValueConstraint`
+**API:** `org.apache.geode.cache.RegionFactory.setValueConstraint`
**Example:**
@@ -1697,7 +1697,7 @@ Expiration setting that specifies how long the region can remain in the cache wi
**Default:** not set - no expiration of this type
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setRegionTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setRegionTimeToLive`
**Example:**
@@ -1788,11 +1788,11 @@ Select one of the following expiration actions:
## <a id="id_l2x_c2q_rr" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -1820,7 +1820,7 @@ To ensure reliable read behavior across the partitioned region, use `region-time
**Default:** not set - no expiration of this type
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setRegionIdleTimeout`
+**API:** `org.apache.geode.cache.RegionFactory.setRegionIdleTimeout`
**Example:**
@@ -1910,11 +1910,11 @@ Select one of the following expiration actions:
## <a id="region-idle-time_custom-expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -1939,7 +1939,7 @@ Expiration setting that specifies how long the region\u2019s entries can remain in
**Default:** not set - no expiration of this type.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setEntryTimeToLive`
**Example:**
@@ -2030,11 +2030,11 @@ Select one of the following expiration actions:
## <a id="entry-time-to-live_custom_expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -2060,7 +2060,7 @@ Expiration setting that specifies how long the region\u2019s entries can remain in
**Note:**
To ensure reliable read behavior across the partitioned region, use `entry-time-to-live` for entry expiration instead of this setting.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setEntryIdleTimeout`
+**API:** `org.apache.geode.cache.RegionFactory.setEntryIdleTimeout`
**Example:**
@@ -2152,11 +2152,11 @@ Select one of the following expiration actions:
## <a id="entry-idle-time_custom-expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -2182,7 +2182,7 @@ Defines the region as partitioned and controls partitioning behavior. This is se
**Note:**
With the exception of `local-max-memory`, all members defining a partitioned region must use the same partition attribute settings.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setPartitionAttributes`
+**API:** `org.apache.geode.cache.RegionFactory.setPartitionAttributes`
<a id="id_thp_h2q_rr__d2116e4014"></a>
@@ -2212,7 +2212,7 @@ With the exception of `local-max-memory`, all members defining a partitioned reg
Describes a custom PartitionResolver for a region.
-**API:** `com.gemstone.gemfire.cache.PartitionAttributesFactory.setPartitionResolver`
+**API:** `org.apache.geode.cache.PartitionAttributesFactory.setPartitionResolver`
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements. See [<class-name> and <parameter>](cache_xml.html#class-name_parameter).
@@ -2245,7 +2245,7 @@ Defines a custom PartitionListener for a partitioned region.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements. See [<class-name> and <parameter>](cache_xml.html#class-name_parameter).
-**API:** `com.gemstone.gemfire.cache.PartitionAttributesFactory.PartitionListener`
+**API:** `org.apache.geode.cache.PartitionAttributesFactory.PartitionListener`
**Example:**
@@ -2264,7 +2264,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
Describes a partition in a Fixed Partitioned Region.
-**API:** `com.gemstone.gemfire.cache.PartitionAttributesFactory.addFixedPartitionAttributes`
+**API:** `org.apache.geode.cache.PartitionAttributesFactory.addFixedPartitionAttributes`
<a id="id_vgx_32q_rr__d2116e4308"></a>
@@ -2302,7 +2302,7 @@ Describes a partition in a Fixed Partitioned Region.
Establishes reliability requirements and behavior for a region. Use this to configure the region to require one or more membership roles to be running in the system for reliable access to the region. You can set up your own roles, such as producer or backup, specifying each role as a string. Membership attributes have no effect unless one or more required roles are specified.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setMembershipAttributes`
+**API:** `org.apache.geode.cache.RegionFactory.setMembershipAttributes`
<a id="id_dsh_j2q_rr__d2116e4408"></a>
@@ -2392,7 +2392,7 @@ Specifies how the region is affected by resumption of reliability when one or mo
Specifies a role that is required for reliable access to the region.
-**API:** `com.gemstone.gemfire.cache.MembershipAttributes`
+**API:** `org.apache.geode.cache.MembershipAttributes`
<a id="id_kfw_j2q_rr__d2116e4568"></a>
@@ -2419,7 +2419,7 @@ Specifies subscriber requirements and behavior for the region. There is one subs
**Note:**
The interest policy determines which events are delivered, but the `data-policy` determines how the events are applied to the cache.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setSubscriptionAttributes`
+**API:** `org.apache.geode.cache.RegionFactory.setSubscriptionAttributes`
<a id="id_a3g_k2q_rr__d2116e4657"></a>
@@ -2477,7 +2477,7 @@ An event-handler plug-in that allows you to program for cache misses. At most, o
For partitioned regions, if you want to have a cache loader, install an instance of the cache loader in every data store. Partitioned regions support partitioned loading, where each cache loader loads only the data entries in the local member. If data redundancy is configured, data is loaded only if the local member holds the primary copy.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCacheLoader`
+**API:** `org.apache.geode.cache.RegionFactory.setCacheLoader`
**Example:**
@@ -2493,7 +2493,7 @@ For partitioned regions, if you want to have a cache loader, install an instance
An event-handler plug-in that allows you to receive before-event notification for changes to the region and its entries. It also has the ability to abort events. At most, one cache writer can be defined in each member for the region. A cache writer may be invoked remotely from other members that have the region defined.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCacheWriter`
+**API:** `org.apache.geode.cache.RegionFactory.setCacheWriter`
**Example:**
@@ -2511,7 +2511,7 @@ An event-handler plug-in that receives after-event notification of changes to th
Specify the Java class for the cache listener and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements. See [<class-name> and <parameter>](cache_xml.html#class-name_parameter).
-**API:** `com.gemstone.gemfire.cache.RegionFactory.addCacheListener`
+**API:** `org.apache.geode.cache.RegionFactory.addCacheListener`
**Example:**
@@ -2548,7 +2548,7 @@ Specifies whether and how to control a region\u2019s size. Size is controlled by re
**Default:** Uses the lru-entry-count algorithm.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setEvictionAttributes`
+**API:** `org.apache.geode.cache.RegionFactory.setEvictionAttributes`
**Example:**
@@ -2937,7 +2937,7 @@ Defines a region in the cache. See [<region-attributes>](cache_xml.html#re
**Default:**
-**API:** `com.gemstone.gemfire.cache.RegionFactory` or `com.gemstone.gemfire.cache.ClientRegionFactory`
+**API:** `org.apache.geode.cache.RegionFactory` or `org.apache.geode.cache.ClientRegionFactory`
<a id="id_q5c_s2q_rr__d2116e5829"></a>
@@ -2978,7 +2978,7 @@ Describes an index to be created on a region. The index node, if any, should all
**Default:**
-**API:** `com.gemstone.gemfire.cache.query.QueryService.createIndex, createKeyIndex, createHashIndex`
+**API:** `org.apache.geode.cache.query.QueryService.createIndex, createKeyIndex, createHashIndex`
<a id="id_kcn_s2q_rr__d2116e5943"></a>
@@ -3021,7 +3021,7 @@ An "entry" element describes an entry to be added to a region. Note that if an e
**Default:**
-**API:** `com.gemstone.gemfire.cache.Region.create`, `put`, `get`, `putAll`, `getAll`
+**API:** `org.apache.geode.cache.Region.create`, `put`, `get`, `putAll`, `getAll`
**Example:**
@@ -3054,7 +3054,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<parameter name="cacheserver">
<declarable>
- <class-name>com.gemstone.gemfire.addon.cache.CacheServerInitializer</class-name>
+ <class-name>org.apache.geode.addon.cache.CacheServerInitializer</class-name>
<parameter name="system.property.prefix">
<string>cacheserver</string>
</parameter>
@@ -3097,7 +3097,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<parameter name="cacheserver">
<declarable>
- <class-name>com.gemstone.gemfire.addon.cache.CacheServerInitializer</class-name>
+ <class-name>org.apache.geode.addon.cache.CacheServerInitializer</class-name>
<parameter name="system.property.prefix">
<string>cacheserver</string>
</parameter>
@@ -3158,7 +3158,7 @@ Specify the Java class for the function and its initialization parameters with t
**Default:**
-**API:** `com.gemstone.gemfire.cache.execute.FunctionService`
+**API:** `org.apache.geode.cache.execute.FunctionService`
**Example:**
@@ -3174,7 +3174,7 @@ Specify the Java class for the function and its initialization parameters with t
A memory monitor that tracks cache size as a percentage of total heap or off-heap memory and controls size by restricting access to the cache and prompting eviction of old entries from the cache. For tenured heap, used in conjunction with settings for JVM memory and Java garbage collection. For off-heap memory, used with the off-heap memory manager.
-**API:** `com.gemstone.gemfire.cache.control.ResourceManager`
+**API:** `org.apache.geode.cache.control.ResourceManager`
<a id="id_yvl_x2q_rr__d2116e6336"></a>
@@ -3260,7 +3260,7 @@ Allows you to configure the DataSerializer for this Geode member. It registers a
Specify the Java class for the `DataSerializer` and its initialization parameters with the `<class-name>` sub-element.
-**API:** You can also register a `DataSerializer` by using the `com.gemstone.gemfire.DataSerializer.register` API. Use the `com.gemstone.gemfire.Instantiator` API to register a `DataSerializable` implementation.
+**API:** You can also register a `DataSerializer` by using the `org.apache.geode.DataSerializer.register` API. Use the `org.apache.geode.Instantiator` API to register a `DataSerializable` implementation.
## <a id="id_p5t_y2q_rr" class="no-quick-link"></a><instantiator>
@@ -3270,7 +3270,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
**API:** `DataSerializable`
-You can also directly specify `<instantiator>` as a sub-element of `<cache>`. Use the `com.gemstone.gemfire.Instantiator` API to register a `DataSerializable` implementation as the serialization framework for the cache. The following table lists the attribute that can be specified for an `<instantiator>`.
+You can also directly specify `<instantiator>` as a sub-element of `<cache>`. Use the `org.apache.geode.Instantiator` API to register a `DataSerializable` implementation as the serialization framework for the cache. The following table lists the attribute that can be specified for an `<instantiator>`.
<a id="id_p5t_y2q_rr__d2116e6596"></a>
@@ -3325,7 +3325,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<parameter name="cacheserver">
<declarable>
- <class-name>com.gemstone.gemfire.addon.cache.CacheServerInitializer</class-name>
+ <class-name>org.apache.geode.addon.cache.CacheServerInitializer</class-name>
<parameter name="system.property.prefix">
<string>cacheserver</string>
</parameter>
@@ -3365,7 +3365,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<parameter name="cacheserver">
<declarable>
- <class-name>com.gemstone.gemfire.addon.cache.CacheServerInitializer</class-name>
+ <class-name>org.apache.geode.addon.cache.CacheServerInitializer</class-name>
<parameter name="system.property.prefix">
<string>cacheserver</string>
</parameter>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/reference/topics/handling_exceptions_and_failures.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/handling_exceptions_and_failures.html.md.erb b/reference/topics/handling_exceptions_and_failures.html.md.erb
index 61f8284..0fd854c 100644
--- a/reference/topics/handling_exceptions_and_failures.html.md.erb
+++ b/reference/topics/handling_exceptions_and_failures.html.md.erb
@@ -6,7 +6,7 @@ Your application needs to catch certain classes to handle all the exceptions and
- `GemFireCheckedException`. This class is the abstract superclass of exceptions that are thrown and declared. Wherever possible, GemFire exceptions are checked exceptions. `GemFireCheckedException` is a Geode version of `java.lang.Exception`.
- `GemFireException`. This class is the abstract superclass of unchecked exceptions that are thrown to indicate conditions for which the developer should not normally need to check. You can look at the subclasses of `GemFireException` to see all the runtime exceptions in the GemFire system; see the class hierarchy in the online Java API documentation. `GemFireException` is a Geode version of java.lang.`RuntimeException`. You can also look at the method details in the `Region` API javadocs for Geode exceptions you may want to catch.
-- `SystemFailure`. In addition to exception management, Geode provides a class to help you manage catastrophic failure in your distributed system, particularly in your application. The Javadocs for this class provide extensive guidance for managing failures in your system and your application. See `SystemFailure` in the `com.gemstone.gemfire` package.
+- `SystemFailure`. In addition to exception management, Geode provides a class to help you manage catastrophic failure in your distributed system, particularly in your application. The Javadocs for this class provide extensive guidance for managing failures in your system and your application. See `SystemFailure` in the `org.apache.geode` package.
To see the exceptions thrown by a specific method, refer to the method's online Java documentation.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/reference/topics/region_shortcuts_reference.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/region_shortcuts_reference.html.md.erb b/reference/topics/region_shortcuts_reference.html.md.erb
index c10da71..f3d9ca9 100644
--- a/reference/topics/region_shortcuts_reference.html.md.erb
+++ b/reference/topics/region_shortcuts_reference.html.md.erb
@@ -115,7 +115,7 @@ Eviction | eviction-algorithm | lru-heap-percentage
<lru-heap-percentage
action="local-destroy">
<class-name>
- com.gemstone.gemfire.internal.size.SizeClassOnceObjectSizer
+ org.apache.geode.internal.size.SizeClassOnceObjectSizer
</class-name>
</lru-heap-percentage>
</eviction-attributes>
@@ -423,7 +423,7 @@ Eviction | eviction-algorithm | lru-heap-percentage
<eviction-attributes>
<lru-heap-percentage
action="local-destroy">
- <class-name>com.gemstone.gemfire.internal.size.SizeClassOnceObjectSizer</class-name>
+ <class-name>org.apache.geode.internal.size.SizeClassOnceObjectSizer</class-name>
</lru-heap-percentage>
</eviction-attributes>
</region-attributes>
@@ -873,7 +873,7 @@ Partition | redundant-copies | 1
<eviction-attributes>
<lru-heap-percentage action="local-destroy">
<class-name>
- com.gemstone.gemfire.internal.size.SizeClassOnceObjectSizer
+ org.apache.geode.internal.size.SizeClassOnceObjectSizer
</class-name>
</lru-heap-percentage>
</eviction-attributes>
@@ -1227,7 +1227,7 @@ Eviction | eviction-algorithm | lru-heap-percentage
<eviction-attributes>
<lru-heap-percentage
action="local-destroy">
- <class-name>com.gemstone.gemfire.internal.size.SizeClassOnceObjectSizer</class-name>
+ <class-name>org.apache.geode.internal.size.SizeClassOnceObjectSizer</class-name>
</lru-heap-percentage>
</eviction-attributes>
</region-attributes>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/develop_rest_apps.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/develop_rest_apps.html.md.erb b/rest_apps/develop_rest_apps.html.md.erb
index a40bf1a..fff34d5 100644
--- a/rest_apps/develop_rest_apps.html.md.erb
+++ b/rest_apps/develop_rest_apps.html.md.erb
@@ -56,7 +56,7 @@ Date: Sat, 18 Jan 2014 20:05:47 GMT
"name": "customers",
"type": "REPLICATE",
"key-constraint": "java.lang.String",
- "value-constraint": "com.gemstone.gemfire.pdx.PdxInstance"
+ "value-constraint": "org.apache.geode.pdx.PdxInstance"
},
{
"name": "items",
@@ -80,7 +80,7 @@ Date: Sat, 18 Jan 2014 20:05:47 GMT
"name": "empty_region",
"type": "EMPTY",
"key-constraint": "java.lang.String",
- "value-constraint": "com.gemstone.gemfire.pdx.PdxInstance"
+ "value-constraint": "org.apache.geode.pdx.PdxInstance"
}
]
}
@@ -216,7 +216,7 @@ POST /gemfire-api/v1/orders?key=2
Accept: application/json
Content-Type: application/json
{
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 112,
"customerId": 1012,
"description": "Purchase Order for myCompany",
@@ -266,7 +266,7 @@ Request Payload: application/json
Content-Type: application/json
Accept: application/json
{
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 1121,
"customerId": 1012,
"description": "Order for XYZ Corp",
@@ -325,7 +325,7 @@ Accept: application/json
Content-Type: application/json
{
"@old": {
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 1121,
"customerId": 1012,
"description": "Order for XYZ Corp",
@@ -346,7 +346,7 @@ Content-Type: application/json
"totalPrice": 225
},
"@new ": {
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 1121,
"customerId": 1013,
"description": "Order for New Corp",
@@ -508,7 +508,7 @@ Content-Type: application/json
"itemNo": 1,
"unitPrice": 20,
"totalPrice": 200,
- "type-class": "com.gemstone.gemfire.web.rest.domain.Item"
+ "type-class": "org.apache.geode.web.rest.domain.Item"
},
{
"description": "Product-BBB",
@@ -516,11 +516,11 @@ Content-Type: application/json
"itemNo": 2,
"unitPrice": 10,
"totalPrice": 150,
- "type-class": "com.gemstone.gemfire.web.rest.domain.Item"
+ "type-class": "org.apache.geode.web.rest.domain.Item"
}
],
"orderDate": "Mon Feb 10 00:00:00 IST 2014",
- "type-class": "com.gemstone.gemfire.web.rest.domain.Order"
+ "type-class": "org.apache.geode.web.rest.domain.Order"
},
{...},
{...}
@@ -557,7 +557,7 @@ Content-Type: application/json
"firstName": "Jane",
"lastName": "Doe",
"customerId": 101,
- "type-class": "com.gemstone.gemfire.web.rest.domain.Customer"
+ "type-class": "org.apache.geode.web.rest.domain.Customer"
}
]
```
@@ -653,7 +653,7 @@ Content-Type: application/json
"@value": 210
},
{
- "@type": "com.gemstone.gemfire.web.rest.domain.Item",
+ "@type": "org.apache.geode.web.rest.domain.Item",
"itemNo": "599",
"description": "Part X Free on Bumper Offer",
"quantity": "2",
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/get_region_data_for_multiple_keys.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/get_region_data_for_multiple_keys.html.md.erb b/rest_apps/get_region_data_for_multiple_keys.html.md.erb
index 2a0f3c1..a855dfa 100644
--- a/rest_apps/get_region_data_for_multiple_keys.html.md.erb
+++ b/rest_apps/get_region_data_for_multiple_keys.html.md.erb
@@ -65,7 +65,7 @@ Date: Sat, 18 Jan 2014 21:39:04 GMT
"orders": [
null,
{
- "@type": "com.gemstone.gemfire.rest.internal.web.controllers.Order",
+ "@type": "org.apache.geode.rest.internal.web.controllers.Order",
"purchaseOrderNo": 1112,
"customerId": 102,
"description": "Purchase order for company - B",
@@ -93,7 +93,7 @@ Date: Sat, 18 Jan 2014 21:39:04 GMT
]
},
{
- "@type": "com.gemstone.gemfire.rest.internal.web.controllers.Order",
+ "@type": "org.apache.geode.rest.internal.web.controllers.Order",
"purchaseOrderNo": 11101,
"customerId": 101,
"description": "Purchase order for company - A",
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/get_regions.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/get_regions.html.md.erb b/rest_apps/get_regions.html.md.erb
index 73b4bc6..6633100 100644
--- a/rest_apps/get_regions.html.md.erb
+++ b/rest_apps/get_regions.html.md.erb
@@ -38,7 +38,7 @@ Date: Sat, 18 Jan 2014 20:05:47 GMT
"name": "customers",
"type": "REPLICATE",
"key-constraint": "java.lang.String",
- "value-constraint": "com.gemstone.gemfire.pdx.PdxInstance"
+ "value-constraint": "org.apache.geode.pdx.PdxInstance"
},
{
"name": "items",
@@ -62,7 +62,7 @@ Date: Sat, 18 Jan 2014 20:05:47 GMT
"name": "empty_region",
"type": "EMPTY",
"key-constraint": "java.lang.String",
- "value-constraint": "com.gemstone.gemfire.pdx.PdxInstance"
+ "value-constraint": "org.apache.geode.pdx.PdxInstance"
}
]
}
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/post_execute_functions.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/post_execute_functions.html.md.erb b/rest_apps/post_execute_functions.html.md.erb
index 019a3ee..ee7064c 100644
--- a/rest_apps/post_execute_functions.html.md.erb
+++ b/rest_apps/post_execute_functions.html.md.erb
@@ -31,7 +31,7 @@ Execute Geode function on entire cluster or on a specified region, members and m
"@value": 210
},
{
- "@type": "com.gemstone.gemfire.web.rest.domain.Item",
+ "@type": "org.apache.geode.web.rest.domain.Item",
"itemNo": "599",
"description": "Part X Free on Bumper Offer",
"quantity": "2",
@@ -55,7 +55,7 @@ Content-Type: application/json
"@value": 210
},
{
- "@type": "com.gemstone.gemfire.web.rest.domain.Item",
+ "@type": "org.apache.geode.web.rest.domain.Item",
"itemNo": "599",
"description": "Part X Free on Bumper Offer",
"quantity": "2",
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/post_execute_query.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/post_execute_query.html.md.erb b/rest_apps/post_execute_query.html.md.erb
index e46d325..38d9341 100644
--- a/rest_apps/post_execute_query.html.md.erb
+++ b/rest_apps/post_execute_query.html.md.erb
@@ -96,7 +96,7 @@ Content-Type: application/json
"itemNo": 1,
"unitPrice": 20,
"totalPrice": 200,
- "type-class": "com.gemstone.gemfire.web.rest.domain.Item"
+ "type-class": "org.apache.geode.web.rest.domain.Item"
},
{
"description": "Product-BBB",
@@ -104,11 +104,11 @@ Content-Type: application/json
"itemNo": 2,
"unitPrice": 10,
"totalPrice": 150,
- "type-class": "com.gemstone.gemfire.web.rest.domain.Item"
+ "type-class": "org.apache.geode.web.rest.domain.Item"
}
],
"orderDate": "Mon Feb 10 00:00:00 IST 2014",
- "type-class": "com.gemstone.gemfire.web.rest.domain.Order"
+ "type-class": "org.apache.geode.web.rest.domain.Order"
},
{...},
{...}
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/post_if_absent_data.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/post_if_absent_data.html.md.erb b/rest_apps/post_if_absent_data.html.md.erb
index 8f7c395..ae1dd52 100644
--- a/rest_apps/post_if_absent_data.html.md.erb
+++ b/rest_apps/post_if_absent_data.html.md.erb
@@ -44,7 +44,7 @@ POST /gemfire-api/v1/orders?key=2
Accept: application/json
Content-Type: application/json
{
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 112,
"customerId": 1012,
"description": "Purchase Order for myCompany",
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/put_multiple_values_for_keys.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/put_multiple_values_for_keys.html.md.erb b/rest_apps/put_multiple_values_for_keys.html.md.erb
index 7a70936..0cb3ed7 100644
--- a/rest_apps/put_multiple_values_for_keys.html.md.erb
+++ b/rest_apps/put_multiple_values_for_keys.html.md.erb
@@ -25,7 +25,7 @@ Accept: application/json
Content-Type: application/json
[
{
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 555,
"customerId": 5,
"description": "Order for 23 Corp",
@@ -46,7 +46,7 @@ Content-Type: application/json
"totalPrice": 99.9
},
{
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 777,
"customerId": 11,
"description": "Order for MNP Corp",
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/put_replace_data.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/put_replace_data.html.md.erb b/rest_apps/put_replace_data.html.md.erb
index 6544ab5..8c03f1f 100644
--- a/rest_apps/put_replace_data.html.md.erb
+++ b/rest_apps/put_replace_data.html.md.erb
@@ -27,7 +27,7 @@ PUT //gemfire-api/v1/orders/2?op=REPLACE
Accept: application/json
Content-Type: application/json
{
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 1121,
"customerId": 1012,
"description": "Order for XYZ Corp",
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/put_update_cas_data.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/put_update_cas_data.html.md.erb b/rest_apps/put_update_cas_data.html.md.erb
index 6538e4c..88ea86c 100644
--- a/rest_apps/put_update_cas_data.html.md.erb
+++ b/rest_apps/put_update_cas_data.html.md.erb
@@ -41,7 +41,7 @@ http://<hostname_or_http-service-bind-address>:<http-service-port>/gemfire-api/v
<td>@old</td>
<td>Compare this value to the existing value in the region.</td>
<td><pre class="pre codeblock"><code>{
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 1121,
"customerId": 1012,
"description": "Order for XYZ Corp",
@@ -66,7 +66,7 @@ http://<hostname_or_http-service-bind-address>:<http-service-port>/gemfire-api/v
<td>@new</td>
<td>If @old value matches existing value, use this value to replace the existing value.</td>
<td><pre class="pre codeblock"><code>{
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 1121,
"customerId": 1013,
"description": "Order for New Corp",
@@ -101,7 +101,7 @@ Accept: application/json
Content-Type: application/json
{
"@old": {
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 1121,
"customerId": 1012,
"description": "Order for XYZ Corp",
@@ -122,7 +122,7 @@ Content-Type: application/json
"totalPrice": 225
},
"@new ": {
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 1121,
"customerId": 1013,
"description": "Order for New Corp",
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/put_update_data.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/put_update_data.html.md.erb b/rest_apps/put_update_data.html.md.erb
index 108c045..0f98c25 100644
--- a/rest_apps/put_update_data.html.md.erb
+++ b/rest_apps/put_update_data.html.md.erb
@@ -22,7 +22,7 @@ Request Payload: application/json
Content-Type: application/json
Accept: application/json
{
- "@type": "com.gemstone.gemfire.web.rest.domain.Order",
+ "@type": "org.apache.geode.web.rest.domain.Order",
"purchaseOrderNo": 1121,
"customerId": 1012,
"description": "Order for XYZ Corp",
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/rest_examples.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/rest_examples.html.md.erb b/rest_apps/rest_examples.html.md.erb
index 18e2de3..3994ff0 100644
--- a/rest_apps/rest_examples.html.md.erb
+++ b/rest_apps/rest_examples.html.md.erb
@@ -30,7 +30,7 @@ The following Java examples assume a project directory structure similar to the
## \#1. REST Java Client (RestClientApp.java)
``` pre
-package com.gemstone.gemfire.restclient;
+package org.apache.geode.restclient;
import org.springframework.http.HttpHeaders;
import org.springframework.http.MediaType;
@@ -40,7 +40,7 @@ package com.gemstone.gemfire.restclient;
import org.springframework.web.client.HttpClientErrorException;
import org.springframework.web.client.HttpServerErrorException;
- import com.gemstone.gemfire.util.RestClientUtils;
+ import org.apache.geode.util.RestClientUtils;
import java.util.ArrayList;
import java.util.List;
@@ -50,7 +50,7 @@ package com.gemstone.gemfire.restclient;
private static final String PEOPLE_REGION = "/People";
private static final String PERSON1_AS_JSON = "{"
- + "\"@type\ ": \"com.gemstone.gemfire.domain.Person\ "," + "\"id\ ": 1,"
+ + "\"@type\ ": \"org.apache.geode.domain.Person\ "," + "\"id\ ": 1,"
+ " \"firstName\ ": \"Jane\ "," + " \"middleName\ ": \"H\ ","
+ " \"lastName\ ": \"Doe1\ "," + " \"birthDate\ ": \"04/12/1983\ ","
+ "\"gender\ ": \"MALE\ "" + "}";
@@ -95,21 +95,21 @@ package com.gemstone.gemfire.restclient;
## \#1a. Geode Cache Java Client (MyJavaClient.java)
``` pre
-package com.gemstone.gemfire.javaclient;
+package org.apache.geode.javaclient;
import java.util.Calendar;
import java.util.HashMap;
import java.util.Map;
- import com.gemstone.gemfire.cache.Region;
- import com.gemstone.gemfire.cache.client.ClientCache;
- import com.gemstone.gemfire.cache.client.ClientCacheFactory;
- import com.gemstone.gemfire.cache.client.ClientRegionFactory;
- import com.gemstone.gemfire.cache.client.ClientRegionShortcut;
- import com.gemstone.gemfire.domain.Gender;
- import com.gemstone.gemfire.domain.Person;
- import com.gemstone.gemfire.pdx.PdxInstance;
- import com.gemstone.gemfire.util.DateTimeUtils;
+ import org.apache.geode.cache.Region;
+ import org.apache.geode.cache.client.ClientCache;
+ import org.apache.geode.cache.client.ClientCacheFactory;
+ import org.apache.geode.cache.client.ClientRegionFactory;
+ import org.apache.geode.cache.client.ClientRegionShortcut;
+ import org.apache.geode.domain.Gender;
+ import org.apache.geode.domain.Person;
+ import org.apache.geode.pdx.PdxInstance;
+ import org.apache.geode.util.DateTimeUtils;
public class MyJavaClient {
@@ -190,7 +190,7 @@ package com.gemstone.gemfire.javaclient;
## \#1b. REST Client Utilities (RestClientUtils.java)
``` pre
-package com.gemstone.gemfire.util;
+package org.apache.geode.util;
import java.net.URI;
@@ -264,7 +264,7 @@ package com.gemstone.gemfire.util;
## \#1c. Date and Time Utilities (DateTimeUtils.java)
``` pre
-package com.gemstone.gemfire.util;
+package org.apache.geode.util;
import java.text.SimpleDateFormat;
@@ -300,17 +300,17 @@ package com.gemstone.gemfire.util;
## \#1d. Person Class (Person.java)
``` pre
-package com.gemstone.gemfire.domain;
+package org.apache.geode.domain;
import java.util.Date;
- import com.gemstone.gemfire.internal.lang.ObjectUtils;
- import com.gemstone.gemfire.pdx.PdxReader;
- import com.gemstone.gemfire.pdx.PdxSerializable;
- import com.gemstone.gemfire.pdx.PdxWriter;
+ import org.apache.geode.internal.lang.ObjectUtils;
+ import org.apache.geode.pdx.PdxReader;
+ import org.apache.geode.pdx.PdxSerializable;
+ import org.apache.geode.pdx.PdxWriter;
- import com.gemstone.gemfire.util.DateTimeUtils;
+ import org.apache.geode.util.DateTimeUtils;
/**
* The Person class is an abstraction modeling a person.
@@ -470,7 +470,7 @@ package com.gemstone.gemfire.domain;
## \#1e. Gender Class (Gender.java)
``` pre
-package com.gemstone.gemfire.domain;
+package org.apache.geode.domain;
/**
* The Gender enum is a enumeration of genders (sexes).
@@ -498,7 +498,7 @@ class JsonSerializable
def to_json
hash = {}
- hash["@type"] = "com.gemstone.gemfire.web.rest.domain.Person"
+ hash["@type"] = "org.apache.geode.web.rest.domain.Person"
self.instance_variables.each do |var|
if !var.to_s.end_with?("links")
hash[var.to_s[1..-1]] = self.instance_variable_get var
@@ -600,7 +600,7 @@ Person is...
Person modified is...
{ type = Person, id = 1, firstName = Jack, middleName = H, lastName = Handy, birthDate = 04/12/1983, gender = MALE}
JSON sent to Server for Person with ID 1...
- {"@type":"com.gemstone.gemfire.web.rest.domain.Person","id":1,"firstName":"Jack","middleName":"H","lastName":"Handy","birthDate":"04/12/1983","gender":"MALE"}
+ {"@type":"org.apache.geode.web.rest.domain.Person","id":1,"firstName":"Jack","middleName":"H","lastName":"Handy","birthDate":"04/12/1983","gender":"MALE"}
```
## \#3. Python REST Client (restClient.py)
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/rest_apps/setup_config.html.md.erb
----------------------------------------------------------------------
diff --git a/rest_apps/setup_config.html.md.erb b/rest_apps/setup_config.html.md.erb
index 4a848b2..e0daa48 100644
--- a/rest_apps/setup_config.html.md.erb
+++ b/rest_apps/setup_config.html.md.erb
@@ -135,7 +135,7 @@ The following procedure starts up a REST API service-enabled Geode deployment:
You can also start up and configure Geode REST services programmatically. For example:
``` pre
- import com.gemstone.gemfire.distributed.ServerLauncher;
+ import org.apache.geode.distributed.ServerLauncher;
public class MyEmbeddedRestServer {
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/gemcached/deploying_gemcached.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/gemcached/deploying_gemcached.html.md.erb b/tools_modules/gemcached/deploying_gemcached.html.md.erb
index bd789fb..b2fbc00 100644
--- a/tools_modules/gemcached/deploying_gemcached.html.md.erb
+++ b/tools_modules/gemcached/deploying_gemcached.html.md.erb
@@ -8,7 +8,7 @@ The following sections describe how to configure and deploy an embedded Gemcache
## <a id="topic_7B158074B27A4FEF9D38E7C369905C72__section_17E7E4058D914334B9C5AC2E3DC1F7F2" class="no-quick-link"></a>Embedding a Gemcached server in a Geode Java Application
-The `com.gemstone.gemfire.memcached` package contains a single class, `GemFireMemcachedServer`. (See the [Geode Javadocs](http://static.springsource.org/spring-gemfire/docs/current/api/).) Use this class to configure and embed a Gemcached server in a Geode cache server. For example, the following statement creates and starts an embedded Gemcached server on port number 5555 using the binary protocol:
+The `org.apache.geode.memcached` package contains a single class, `GemFireMemcachedServer`. (See the [Geode Javadocs](http://static.springsource.org/spring-gemfire/docs/current/api/).) Use this class to configure and embed a Gemcached server in a Geode cache server. For example, the following statement creates and starts an embedded Gemcached server on port number 5555 using the binary protocol:
``` pre
GemFireMemcachedServer server =
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/gfsh/command-pages/create.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/gfsh/command-pages/create.html.md.erb b/tools_modules/gfsh/command-pages/create.html.md.erb
index 92b652b..9864fb2 100644
--- a/tools_modules/gfsh/command-pages/create.html.md.erb
+++ b/tools_modules/gfsh/command-pages/create.html.md.erb
@@ -211,7 +211,7 @@ If index creation fails, you may receive an error message in gfsh similar to the
``` pre
gfsh>create defined indexes
-Exception : com.gemstone.gemfire.cache.query.RegionNotFoundException ,
+Exception : org.apache.geode.cache.query.RegionNotFoundException ,
Message : Region ' /r3' not found: from /r3Occurred on following members
1. india(s1:17866)<v1>:27809
```
@@ -889,7 +889,7 @@ See [Region Data Storage and Distribution](../../../developing/region_options/ch
</tr>
<tr class="even">
<td><span class="keyword parmname">\-\-compressor</span></td>
-<td>Java class name that implements compression for the region. You can write a custom compressor that implements <code class="ph codeph">com.gemstone.gemfire.compression.Compressor</code> or you can specify the Snappy compressor (<code class="ph codeph">com.gemstone.gemfire.compression.SnappyCompressor</code>), which is bundled with Geode. See <a href="../../../managing/region_compression/region_compression.html#topic_r43_wgc_gl">Region Compression</a>.</td>
+<td>Java class name that implements compression for the region. You can write a custom compressor that implements <code class="ph codeph">org.apache.geode.compression.Compressor</code> or you can specify the Snappy compressor (<code class="ph codeph">org.apache.geode.compression.SnappyCompressor</code>), which is bundled with Geode. See <a href="../../../managing/region_compression/region_compression.html#topic_r43_wgc_gl">Region Compression</a>.</td>
<td>no compression</td>
</tr>
<tr class="odd">
@@ -906,22 +906,22 @@ See [Region Data Storage and Distribution](../../../developing/region_options/ch
``` pre
create region --name=region1 --type=REPLICATE_PERSISTENT \
---cache-writer=com.gemstone.gemfire.examples.MyCacheWriter \
+--cache-writer=org.apache.geode.examples.MyCacheWriter \
--group=Group1 --disk-store=DiskStore1
create region --name=region12 --template-region=/region1
create region --name=region2 --type=REPLICATE \
---cache-listener=com.gemstone.gemfire.examples.MyCacheListener1,\
-com.gemstone.gemfire.examples.MyCacheListener2 \
+--cache-listener=org.apache.geode.examples.MyCacheListener1,\
+org.apache.geode.examples.MyCacheListener2 \
--group=Group1,Group2
create region --name=region3 --type=PARTITION_PERSISTENT --redundant-copies=2 --total-max-memory=1000 \
--startup-recovery-delay=5 --total-num-buckets=100 --disk-store=DiskStore2 \
---cache-listener=com.gemstone.gemfire.examples.MyCacheListener3 \
+--cache-listener=org.apache.geode.examples.MyCacheListener3 \
--group=Group2
-create region --name=region4 --type=REPLICATE_PROXY --cache-listener=com.gemstone.gemfire.examples.MyCacheListener1
+create region --name=region4 --type=REPLICATE_PROXY --cache-listener=org.apache.geode.examples.MyCacheListener1
--group=Group1,Group2
```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/gfsh/getting_started_gfsh.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/gfsh/getting_started_gfsh.html.md.erb b/tools_modules/gfsh/getting_started_gfsh.html.md.erb
index bc312fa..239114c 100644
--- a/tools_modules/gfsh/getting_started_gfsh.html.md.erb
+++ b/tools_modules/gfsh/getting_started_gfsh.html.md.erb
@@ -114,7 +114,7 @@ by using the backslash character ('\\') as a delimiter. For example:
``` pre
gfsh>create region --name=region1 \
--type=REPLICATE_PERSISTENT \
---cache-writer=com.gemstone.gemfire.examples.MyCacheWriter \
+--cache-writer=org.apache.geode.examples.MyCacheWriter \
--group=Group1 --disk-store=DiskStore1
```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/hibernate_cache/changing_gemfire_default_cfg.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/hibernate_cache/changing_gemfire_default_cfg.html.md.erb b/tools_modules/hibernate_cache/changing_gemfire_default_cfg.html.md.erb
index 58e72fc..0424a58 100644
--- a/tools_modules/hibernate_cache/changing_gemfire_default_cfg.html.md.erb
+++ b/tools_modules/hibernate_cache/changing_gemfire_default_cfg.html.md.erb
@@ -125,13 +125,13 @@ In a Hibernate application, the caching of query results is recommended for quer
## <a id="changing_gemfire_default_cfg__section_E884BF4251D6494695408B30D1F350B1" class="no-quick-link"></a>Remapping the Hibernate EnumType with the Geode EnumType
-Due to an issue with Hibernate in a client-server topology, application classes must be present on the Geode cache server when a Hibernate application uses annotations. If you do not want to place the application classes on the Geode cache server, you can modify the Hibernate configuration to use the `com.gemstone.gemfire.modules.hibernate.EnumType` in place of `org.hibernate.type.EnumType`.
+Due to an issue with Hibernate in a client-server topology, application classes must be present on the Geode cache server when a Hibernate application uses annotations. If you do not want to place the application classes on the Geode cache server, you can modify the Hibernate configuration to use the `org.apache.geode.modules.hibernate.EnumType` in place of `org.hibernate.type.EnumType`.
To configure Hibernate to use the Geode EnumType, modify `hibernate.cfg.xml` to add a property for the mapping. For example:
``` pre
<property name="myEnum">
- <type name="com.gemstone.gemfire.modules.hibernate.EnumType">
+ <type name="org.apache.geode.modules.hibernate.EnumType">
<param name="enumClass">com.mycompany.MyEnum</param>
</type>
</property>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/hibernate_cache/setting_up_the_module.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/hibernate_cache/setting_up_the_module.html.md.erb b/tools_modules/hibernate_cache/setting_up_the_module.html.md.erb
index e304280..cc3702e 100644
--- a/tools_modules/hibernate_cache/setting_up_the_module.html.md.erb
+++ b/tools_modules/hibernate_cache/setting_up_the_module.html.md.erb
@@ -21,7 +21,7 @@ Edit the `hibernate.cfg.xml` file to use the Hibernate Cache module.
``` pre
<property name="hibernate.cache.region.factory_class">
- com.gemstone.gemfire.modules.hibernate.GemFireRegionFactory
+ org.apache.geode.modules.hibernate.GemFireRegionFactory
</property>
```
@@ -84,7 +84,7 @@ Edit the `hibernate.cfg.xml` file to use the Hibernate Cache module.
Similar to Hibernate, Geode uses Simple Logging Facade for Java (SLF4J) to log messages. Upon successful startup, Geode will log the following message:
``` pre
- 2010-11-15 INFO [com.gemstone.gemfire.modules.hibernate.GemFireRegionFactory] -
+ 2010-11-15 INFO [org.apache.geode.modules.hibernate.GemFireRegionFactory] -
<Initializing Apache Geode Modules Version 1.1>
```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/quick_start.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/http_session_mgmt/quick_start.html.md.erb b/tools_modules/http_session_mgmt/quick_start.html.md.erb
index 9b4f70e..b349bb8 100644
--- a/tools_modules/http_session_mgmt/quick_start.html.md.erb
+++ b/tools_modules/http_session_mgmt/quick_start.html.md.erb
@@ -63,7 +63,7 @@ These steps provide a basic starting point for using the Tomcat module. For more
For example, in a peer-to-peer configuration using Tomcat 7, you would add the following entry within the `<server>` element of server.xml:
``` pre
- <Listener className="com.gemstone.gemfire.modules.session.catalina.
+ <Listener className="org.apache.geode.modules.session.catalina.
PeerToPeerCacheLifecycleListener"
locator="localhost[10334]" />
```
@@ -71,7 +71,7 @@ These steps provide a basic starting point for using the Tomcat module. For more
and the following entry within the `<context>` tag in the context.xml file:
``` pre
- <Manager className="com.gemstone.gemfire.modules.session.catalina.
+ <Manager className="org.apache.geode.modules.session.catalina.
Tomcat7DeltaSessionManager"/>
```
[25/50] [abbrv] incubator-geode git commit: GEODE-37 Package renaming
[#118023839]
Posted by rv...@apache.org.
GEODE-37 Package renaming [#118023839]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/23e2f5ce
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/23e2f5ce
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/23e2f5ce
Branch: refs/staging/docs-grant1
Commit: 23e2f5cecd7c6271e43985d2ba71441010991c32
Parents: 27455f0
Author: Dave Barnes <db...@pivotal.io>
Authored: Thu Sep 8 14:36:22 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Thu Sep 8 14:36:22 2016 -0700
----------------------------------------------------------------------
.../managing_data_entries.html.md.erb | 2 +-
.../create_a_region_with_API.html.md.erb | 4 +-
.../managing_data_regions.html.md.erb | 26 ++--
.../data_regions/region_shortcuts.html.md.erb | 6 +-
.../store_retrieve_region_shortcuts.html.md.erb | 2 +-
.../setting_distributed_properties.html.md.erb | 2 +-
.../intro_cache_management.html.md.erb | 10 +-
.../setting_cache_initializer.html.md.erb | 2 +-
.../setting_cache_properties.html.md.erb | 2 +-
.../cluster_config/gfsh_persist.html.md.erb | 2 +-
.../running/running_the_cacheserver.html.md.erb | 6 +-
.../running/running_the_locator.html.md.erb | 8 +-
...implementing_continuous_querying.html.md.erb | 6 +-
.../auto_serialization.html.md.erb | 4 +-
.../jsonformatter_pdxinstances.html.md.erb | 2 +-
.../use_pdx_serializable.html.md.erb | 8 +-
.../use_pdx_serializer.html.md.erb | 10 +-
.../chapter_overview.html.md.erb | 14 +--
.../delta_propagation_example.html.md.erb | 4 +-
.../implementing_delta_propagation.html.md.erb | 4 +-
.../how_distribution_works.html.md.erb | 2 +-
.../locking_in_global_regions.html.md.erb | 4 +-
.../managing_distributed_regions.html.md.erb | 2 +-
.../filtering_multisite_events.html.md.erb | 12 +-
...mplementing_cache_event_handlers.html.md.erb | 10 +-
...ist_of_event_handlers_and_events.html.md.erb | 6 +-
.../resolving_multisite_conflicts.html.md.erb | 2 +-
..._callbacks_that_modify_the_cache.html.md.erb | 4 +-
.../configuring_data_eviction.html.md.erb | 4 +-
.../configuring_data_expiration.html.md.erb | 2 +-
.../function_execution.html.md.erb | 10 +-
.../how_function_execution_works.html.md.erb | 4 +-
.../chapter_overview.html.md.erb | 2 +-
.../implementing_data_loaders.html.md.erb | 4 +-
.../moving_partitioned_data.html.md.erb | 4 +-
...using_custom_partition_resolvers.html.md.erb | 6 +-
.../create_multiple_indexes.html.md.erb | 2 +-
.../querying_basics/running_a_query.html.md.erb | 4 +-
.../dynamic_region_creation.html.md.erb | 42 +++----
.../storing_data_on_disk.html.md.erb | 6 +-
.../transactions/JTA_transactions.html.md.erb | 2 +-
.../transactional_function_example.html.md.erb | 4 +-
.../querying_quick_reference.html.md.erb | 4 +-
getting_started/setup_classpath.html.md.erb | 4 +-
.../disk_store_configuration_params.html.md.erb | 2 +-
managing/heap_use/heap_management.html.md.erb | 4 +-
.../heap_use/off_heap_management.html.md.erb | 2 +-
managing/logging/logging_categories.html.md.erb | 6 +-
managing/logging/logging_whats_next.html.md.erb | 2 +-
.../management/list_of_mbeans_full.html.md.erb | 22 ++--
.../management_system_overview.html.md.erb | 4 +-
managing/management/mm_overview.html.md.erb | 2 +-
.../management/programming_example.html.md.erb | 20 +--
.../performance_controls.html.md.erb | 2 +-
..._controls_controlling_socket_use.html.md.erb | 2 +-
..._controls_setting_cache_timeouts.html.md.erb | 4 +-
.../sockets_and_gateways.html.md.erb | 2 +-
.../region_compression.html.md.erb | 6 +-
.../authentication_examples.html.md.erb | 10 +-
.../how_authorization_works.html.md.erb | 2 +-
.../implementing_authentication.html.md.erb | 4 +-
.../implementing_authorization.html.md.erb | 2 +-
.../application_defined_statistics.html.md.erb | 2 +-
.../diagnosing_system_probs.html.md.erb | 22 ++--
.../recovering_from_p2p_crashes.html.md.erb | 2 +-
.../system_failure_and_recovery.html.md.erb | 10 +-
reference/topics/cache_xml.html.md.erb | 110 ++++++++---------
reference/topics/client-cache.html.md.erb | 80 ++++++------
reference/topics/elements_ref.html.md.erb | 8 +-
reference/topics/gfe_cache_xml.html.md.erb | 122 +++++++++----------
...handling_exceptions_and_failures.html.md.erb | 2 +-
.../region_shortcuts_reference.html.md.erb | 8 +-
rest_apps/develop_rest_apps.html.md.erb | 22 ++--
...et_region_data_for_multiple_keys.html.md.erb | 4 +-
rest_apps/get_regions.html.md.erb | 4 +-
rest_apps/post_execute_functions.html.md.erb | 4 +-
rest_apps/post_execute_query.html.md.erb | 6 +-
rest_apps/post_if_absent_data.html.md.erb | 2 +-
.../put_multiple_values_for_keys.html.md.erb | 4 +-
rest_apps/put_replace_data.html.md.erb | 2 +-
rest_apps/put_update_cas_data.html.md.erb | 8 +-
rest_apps/put_update_data.html.md.erb | 2 +-
rest_apps/rest_examples.html.md.erb | 48 ++++----
rest_apps/setup_config.html.md.erb | 2 +-
.../gemcached/deploying_gemcached.html.md.erb | 2 +-
.../gfsh/command-pages/create.html.md.erb | 14 +--
.../gfsh/getting_started_gfsh.html.md.erb | 2 +-
.../changing_gemfire_default_cfg.html.md.erb | 4 +-
.../setting_up_the_module.html.md.erb | 4 +-
.../http_session_mgmt/quick_start.html.md.erb | 4 +-
.../session_state_log_files.html.md.erb | 14 +--
.../tc_setting_up_the_module.html.md.erb | 2 +-
.../tomcat_changing_gf_default_cfg.html.md.erb | 10 +-
.../tomcat_setting_up_the_module.html.md.erb | 14 +--
...weblogic_changing_gf_default_cfg.html.md.erb | 4 +-
.../weblogic_setting_up_the_module.html.md.erb | 8 +-
tools_modules/pulse/quickstart.html.md.erb | 2 +-
.../chapter_overview.html.md.erb | 2 +-
.../client_server_whats_next.html.md.erb | 4 +-
.../using_bind_addresses.html.md.erb | 2 +-
100 files changed, 467 insertions(+), 467 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
----------------------------------------------------------------------
diff --git a/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb b/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
index 7d54e5a..d809635 100644
--- a/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
+++ b/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
@@ -85,7 +85,7 @@ Always change your entries using copies of the retrieved objects\u2014never directl
`EntryEvent.getOldValue`
`Query.select`
-2. Create a copy of the returned object and work with that. For objects that are cloneable or serializable, you can copy the entry value to a new object using `com.gemstone.gemfire.CopyHelper.copy`. Example:
+2. Create a copy of the returned object and work with that. For objects that are cloneable or serializable, you can copy the entry value to a new object using `org.apache.geode.CopyHelper.copy`. Example:
``` pre
Object o = (StringBuffer)region.get("stringBuf");
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/basic_config/data_regions/create_a_region_with_API.html.md.erb
----------------------------------------------------------------------
diff --git a/basic_config/data_regions/create_a_region_with_API.html.md.erb b/basic_config/data_regions/create_a_region_with_API.html.md.erb
index 302c131..ba8e384 100644
--- a/basic_config/data_regions/create_a_region_with_API.html.md.erb
+++ b/basic_config/data_regions/create_a_region_with_API.html.md.erb
@@ -13,10 +13,10 @@ Region creation is subject to attribute consistency checks, both internal to the
Use a region shortcut to create your region factory.
-
- In peers and servers, use `com.gemstone.gemfire.cache.RegionFactory`.
+ In peers and servers, use `org.apache.geode.cache.RegionFactory`.
-
- In clients, use `com.gemstone.gemfire.cache.client.ClientRegionFactory`.
+ In clients, use `org.apache.geode.cache.client.ClientRegionFactory`.
2.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/basic_config/data_regions/managing_data_regions.html.md.erb
----------------------------------------------------------------------
diff --git a/basic_config/data_regions/managing_data_regions.html.md.erb b/basic_config/data_regions/managing_data_regions.html.md.erb
index bc3e0ad..cd9427b 100644
--- a/basic_config/data_regions/managing_data_regions.html.md.erb
+++ b/basic_config/data_regions/managing_data_regions.html.md.erb
@@ -7,7 +7,7 @@ Apache Geode provides different APIs and XML configuration models to support con
<a id="data_regions__section_18A9481217204613958897FE64105097"></a>
You store your data in region entry key/value pairs, with keys and values being any object types your application needs.
-The `com.gemstone.gemfire.cache.Region` interface implements `java.util.Map`.
+The `org.apache.geode.cache.Region` interface implements `java.util.Map`.
Each region's attributes define how the data in the region is stored, distributed, and managed. Data regions can be distributed, partitioned among system members, or local to the member.
@@ -20,21 +20,21 @@ If you change attributes that define a region, you must restart the member for t
Geode's regions APIs provide specialized behavior for different system member types.
-- **Peer/Server Region APIs**. Use these methods, interfaces, and classes for peer/server region creation. These are in the `com.gemstone.gemfire.cache` package. They correspond to declarations in the `<cache>` element for creating and configuring regions.
- - **`com.gemstone.gemfire.cache.Cache.createRegionFactory`** . This method takes a `RegionShortcut` `enum` to initiate region configuration, and returns a `RegionFactory`. Use `createRegionFactory()`, not "`new RegionFactory`," to create a RegionFactory.
- - **`com.gemstone.gemfire.cache.RegionFactory`**. Provides methods to set individual region attributes and to create the region. The `create` call returns `Region`.
- - **`com.gemstone.gemfire.cache.RegionShortcut`**. Common region configurations can be retrieved through `Cache` `createRegionShortcut` and with the region attribute, `refid`.
-- **Client Region APIs**. Use these methods, interfaces, and classes for client region creation. These are in the `com.gemstone.gemfire.cache.client` package. They correspond to declarations in the `<client-cache>` element for creating and configuring regions.
+- **Peer/Server Region APIs**. Use these methods, interfaces, and classes for peer/server region creation. These are in the `org.apache.geode.cache` package. They correspond to declarations in the `<cache>` element for creating and configuring regions.
+ - **`org.apache.geode.cache.Cache.createRegionFactory`** . This method takes a `RegionShortcut` `enum` to initiate region configuration, and returns a `RegionFactory`. Use `createRegionFactory()`, not "`new RegionFactory`," to create a RegionFactory.
+ - **`org.apache.geode.cache.RegionFactory`**. Provides methods to set individual region attributes and to create the region. The `create` call returns `Region`.
+ - **`org.apache.geode.cache.RegionShortcut`**. Common region configurations can be retrieved through `Cache` `createRegionShortcut` and with the region attribute, `refid`.
+- **Client Region APIs**. Use these methods, interfaces, and classes for client region creation. These are in the `org.apache.geode.cache.client` package. They correspond to declarations in the `<client-cache>` element for creating and configuring regions.
These are client versions of the Peer/Server Region APIs. These client APIs provide similar functionality, but are tailored to the needs and behaviors of client regions.
- - **`com.gemstone.gemfire.cache.clientCache.createRegionFactory`** . This method takes a `ClientRegionShortcut` `enum` to initiate region configuration, and returns a `ClientRegionFactory`.
- - **`com.gemstone.gemfire.cache.client.ClientRegionFactory`**. Provides methods to set individual region attributes and to create the region. The `create` call returns `Region`.
- - **`com.gemstone.gemfire.cache.client.ClientRegionShortcut`** . Common region configurations can be retrieved through `ClientCache` `createClientRegionFactory` and with the region attribute, `refid`.
-- **Region APIs Used For All Member Types**. These interfaces and classes are used universally for region management. These are in the `com.gemstone.gemfire.cache` package. They correspond to declarations under the `<cache>` and `<client-cache>` elements for creating and configuring regions.
- - **`com.gemstone.gemfire.cache.Region`** . Interface for managing your regions and their entries.
- - **`com.gemstone.gemfire.cache.RegionAttributes`** . Object holding region configuration settings.
- - **`com.gemstone.gemfire.cache.createRegionFactory`**. Can be used to create `RegionAttributes` to pass to `RegionFactory` and `ClientRegionFactory`.
+ - **`org.apache.geode.cache.clientCache.createRegionFactory`** . This method takes a `ClientRegionShortcut` `enum` to initiate region configuration, and returns a `ClientRegionFactory`.
+ - **`org.apache.geode.cache.client.ClientRegionFactory`**. Provides methods to set individual region attributes and to create the region. The `create` call returns `Region`.
+ - **`org.apache.geode.cache.client.ClientRegionShortcut`** . Common region configurations can be retrieved through `ClientCache` `createClientRegionFactory` and with the region attribute, `refid`.
+- **Region APIs Used For All Member Types**. These interfaces and classes are used universally for region management. These are in the `org.apache.geode.cache` package. They correspond to declarations under the `<cache>` and `<client-cache>` elements for creating and configuring regions.
+ - **`org.apache.geode.cache.Region`** . Interface for managing your regions and their entries.
+ - **`org.apache.geode.cache.RegionAttributes`** . Object holding region configuration settings.
+ - **`org.apache.geode.cache.createRegionFactory`**. Can be used to create `RegionAttributes` to pass to `RegionFactory` and `ClientRegionFactory`.
## <a id="data_regions__section_9F898C23D2164ED5BB3789FD8B1F68C3" class="no-quick-link"></a>Create and Access Data Regions
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/basic_config/data_regions/region_shortcuts.html.md.erb
----------------------------------------------------------------------
diff --git a/basic_config/data_regions/region_shortcuts.html.md.erb b/basic_config/data_regions/region_shortcuts.html.md.erb
index bcbded8..270987b 100644
--- a/basic_config/data_regions/region_shortcuts.html.md.erb
+++ b/basic_config/data_regions/region_shortcuts.html.md.erb
@@ -42,14 +42,14 @@ You can create your own named attributes as needed, by providing an `id` in your
You can select the most common region attributes settings from Geode\u2019s predefined named region attributes in these classes:
-- **`com.gemstone.gemfire.cache.RegionShortcut`**. For peers and servers.
-- **`com.gemstone.gemfire.cache.client.ClientRegionShortcut`**. For clients.
+- **`org.apache.geode.cache.RegionShortcut`**. For peers and servers.
+- **`org.apache.geode.cache.client.ClientRegionShortcut`**. For clients.
Shortcut attributes are a convenience only. They are just named attributes that Geode has already stored for you. You can override their settings by storing new attributes with the same id as the predefined attributes.
For a full list of all available region shortcuts, see [Region Shortcuts Quick Reference](../../reference/topics/region_shortcuts_table.html#reference_ufj_5kz_4k).
-The `com.gemstone.gemfire.cache.RegionShortcut` Javadocs give complete listings of the options.
+The `org.apache.geode.cache.RegionShortcut` Javadocs give complete listings of the options.
## <a id="region_shortcuts__section_D0975C76572E41F79C1A6EE7CF371251" class="no-quick-link"></a>RegionShortcuts for Peers and Servers
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/basic_config/data_regions/store_retrieve_region_shortcuts.html.md.erb
----------------------------------------------------------------------
diff --git a/basic_config/data_regions/store_retrieve_region_shortcuts.html.md.erb b/basic_config/data_regions/store_retrieve_region_shortcuts.html.md.erb
index fdb5723..9d39bd5 100644
--- a/basic_config/data_regions/store_retrieve_region_shortcuts.html.md.erb
+++ b/basic_config/data_regions/store_retrieve_region_shortcuts.html.md.erb
@@ -5,7 +5,7 @@ title: Storing and Retrieving Region Shortcuts and Custom Named Region Attribut
Use these examples to get started with Geode region shortcuts.
<a id="region_shortcuts__section_D9E58754D2B0435FA2986DBBF3063D4C"></a>
-Geode region shortcuts, in `com.gemstone.gemfire.cache.RegionShortcut` for peers and servers and `com.gemstone.gemfire.cache.client.ClientRegionShortcut` for clients, are available wherever you create a region in the `cache.xml` or through the API. Custom named attributes, stored by you, are available from the moment you store them on.
+Geode region shortcuts, in `org.apache.geode.cache.RegionShortcut` for peers and servers and `org.apache.geode.cache.client.ClientRegionShortcut` for clients, are available wherever you create a region in the `cache.xml` or through the API. Custom named attributes, stored by you, are available from the moment you store them on.
The region shortcuts are special Geode named region attributes, with identifying names. Create custom named region attributes by setting the attributes and storing them with a unique identifier in the region attribute `id`. Retrieve named attributes by providing the shortcut enum value or the name you assigned in the `id` to the region creation:
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/basic_config/gemfire_properties/setting_distributed_properties.html.md.erb
----------------------------------------------------------------------
diff --git a/basic_config/gemfire_properties/setting_distributed_properties.html.md.erb b/basic_config/gemfire_properties/setting_distributed_properties.html.md.erb
index 7f810d3..db03d15 100644
--- a/basic_config/gemfire_properties/setting_distributed_properties.html.md.erb
+++ b/basic_config/gemfire_properties/setting_distributed_properties.html.md.erb
@@ -59,6 +59,6 @@ Set distributed system properties by any combination of the following. The syste
disable-tcp=false
```
-4. Default value. The default property values are listed in the online Java documentation for `com.gemstone.gemfire.distributed.DistributedSystem`.
+4. Default value. The default property values are listed in the online Java documentation for `org.apache.geode.distributed.DistributedSystem`.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/basic_config/the_cache/intro_cache_management.html.md.erb
----------------------------------------------------------------------
diff --git a/basic_config/the_cache/intro_cache_management.html.md.erb b/basic_config/the_cache/intro_cache_management.html.md.erb
index 037c051..2d21a60 100644
--- a/basic_config/the_cache/intro_cache_management.html.md.erb
+++ b/basic_config/the_cache/intro_cache_management.html.md.erb
@@ -5,7 +5,7 @@ title: Introduction to Cache Management
The cache provides in-memory storage and management for your data.
<a id="concept_F8BA7F2D3B5A40D78461E78BC5FB31FA__section_B364B076EB5843DAAC28EE2805686453"></a>
-You organize your data in the cache into *data regions*, each with its own configurable behavior. You store your data into your regions in key/value pairs called *data entries*. The cache also provides features like transactions, data querying, disk storage management, and logging. See the Javadocs for `com.gemstone.gemfire.cache.Cache`.
+You organize your data in the cache into *data regions*, each with its own configurable behavior. You store your data into your regions in key/value pairs called *data entries*. The cache also provides features like transactions, data querying, disk storage management, and logging. See the Javadocs for `org.apache.geode.cache.Cache`.
You generally configure caches using the `gfsh` command-line utility or a combination of XML declarations and API calls. Geode loads and processes your XML declarations when you first create the cache.
@@ -15,10 +15,10 @@ Geode has one cache type for managing server and peer caches and one for managin
Geode's caching APIs provide specialized behavior for different system member types and security settings.
-- **`com.gemstone.gemfire.cache.RegionService`**. Generally, you use the `RegionService` functionality through instances of `Cache` and `ClientCache`. You only specifically use instances of `RegionService` for limited-access users in secure client applications that service many users. The `RegionService` API provides access to existing cache data regions and to the standard query service for the cache. For client caches, queries are sent to the server tier. For server and peer caches, queries are run in the current cache and any available peers. `RegionService` is implemented by `GemFireCache`.
-- **`com.gemstone.gemfire.cache.GemFireCache`**. You do not specifically use instances of `GemFireCache`, but you use `GemFireCache` functionality in your instances of `Cache` and `ClientCache`. `GemFireCache` extends `RegionService` and adds general caching features like region attributes, disk stores for region persistence and overflow, and access to the underlying distributed system. `GemFireCache` is implemented by `Cache` and `ClientCache`.
-- **`com.gemstone.gemfire.cache.Cache`**. Use the `Cache` interface to manage server and peer caches. You have one `Cache` per server or peer process. The `Cache` extends `GemFireCache` and adds server/peer caching features like communication within the distributed system, region creation, transactions and querying, and cache server functionality.
-- **`com.gemstone.gemfire.cache.ClientCache`**. Use the `ClientCache` interface to manage the cache in your clients. You have one `ClientCache` per client process. The `ClientCache` extends `GemFireCache` and adds client-specific caching features like client region creation, subscription keep-alive management for durable clients, querying on server and client tiers, and RegionService creation for secure access by multiple users within the client.
+- **`org.apache.geode.cache.RegionService`**. Generally, you use the `RegionService` functionality through instances of `Cache` and `ClientCache`. You only specifically use instances of `RegionService` for limited-access users in secure client applications that service many users. The `RegionService` API provides access to existing cache data regions and to the standard query service for the cache. For client caches, queries are sent to the server tier. For server and peer caches, queries are run in the current cache and any available peers. `RegionService` is implemented by `GemFireCache`.
+- **`org.apache.geode.cache.GemFireCache`**. You do not specifically use instances of `GemFireCache`, but you use `GemFireCache` functionality in your instances of `Cache` and `ClientCache`. `GemFireCache` extends `RegionService` and adds general caching features like region attributes, disk stores for region persistence and overflow, and access to the underlying distributed system. `GemFireCache` is implemented by `Cache` and `ClientCache`.
+- **`org.apache.geode.cache.Cache`**. Use the `Cache` interface to manage server and peer caches. You have one `Cache` per server or peer process. The `Cache` extends `GemFireCache` and adds server/peer caching features like communication within the distributed system, region creation, transactions and querying, and cache server functionality.
+- **`org.apache.geode\u2248setting_cache_initializer.cache.ClientCache`**. Use the `ClientCache` interface to manage the cache in your clients. You have one `ClientCache` per client process. The `ClientCache` extends `GemFireCache` and adds client-specific caching features like client region creation, subscription keep-alive management for durable clients, querying on server and client tiers, and RegionService creation for secure access by multiple users within the client.
## <a id="concept_F8BA7F2D3B5A40D78461E78BC5FB31FA__section_6486BDAF06EC4B91A548872066F3EC8C" class="no-quick-link"></a>The Cache XML
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/basic_config/the_cache/setting_cache_initializer.html.md.erb
----------------------------------------------------------------------
diff --git a/basic_config/the_cache/setting_cache_initializer.html.md.erb b/basic_config/the_cache/setting_cache_initializer.html.md.erb
index 9016cea..20cc2c6 100644
--- a/basic_config/the_cache/setting_cache_initializer.html.md.erb
+++ b/basic_config/the_cache/setting_cache_initializer.html.md.erb
@@ -27,7 +27,7 @@ Here's the corresponding class definition:
``` pre
-import com.gemstone.gemfire.cache.Declarable;
+import org.apache.geode.cache.Declarable;
public class MyInitializer implements Declarable {
public void init(Properties properties) {
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/basic_config/the_cache/setting_cache_properties.html.md.erb
----------------------------------------------------------------------
diff --git a/basic_config/the_cache/setting_cache_properties.html.md.erb b/basic_config/the_cache/setting_cache_properties.html.md.erb
index 4a2cec1..76d5066 100644
--- a/basic_config/the_cache/setting_cache_properties.html.md.erb
+++ b/basic_config/the_cache/setting_cache_properties.html.md.erb
@@ -17,6 +17,6 @@ Configure the cache and its data regions through one or more of these methods:
As you issue commands, gfsh saves a set of configurations that apply to the entire cluster and also saves configurations that only apply to defined groups of members within the cluster. You can re-use these configurations to create a distributed system. See [Overview of the Cluster Configuration Service](../../configuring/cluster_config/gfsh_persist.html).
- Through declarations in the XML file named in the `cache-xml-file` `gemfire.properties` setting. This file is generally referred to as the `cache.xml` file, but it can have any name. See [cache.xml](../../reference/topics/chapter_overview_cache_xml.html#cache_xml).
-- Through application calls to the `com.gemstone.gemfire.cache.CacheFactory`, `com.gemstone.gemfire.cache.Cache` and `com.gemstone.gemfire.cache.Region` APIs.
+- Through application calls to the `org.apache.geode.cache.CacheFactory`, `org.apache.geode.cache.Cache` and `org.apache.geode.cache.Region` APIs.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/configuring/cluster_config/gfsh_persist.html.md.erb
----------------------------------------------------------------------
diff --git a/configuring/cluster_config/gfsh_persist.html.md.erb b/configuring/cluster_config/gfsh_persist.html.md.erb
index eaa4c62..85be33c 100644
--- a/configuring/cluster_config/gfsh_persist.html.md.erb
+++ b/configuring/cluster_config/gfsh_persist.html.md.erb
@@ -78,7 +78,7 @@ There are some configurations that you cannot create using `gfsh`, and that you
- `pdx-serializer`
**Note:**
- The `configure pdx` command always specifies the <span class="keyword apiname">com.gemstone.gemfire.pdx.ReflectionBasedAutoSerializer</span> class. You cannot specify a custom PDX serializer in gfsh.
+ The `configure pdx` command always specifies the `org.apache.geode.pdx.ReflectionBasedAutoSerializer` class. You cannot specify a custom PDX serializer in gfsh.
- `custom-expiry`
- `initializer`
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/configuring/running/running_the_cacheserver.html.md.erb
----------------------------------------------------------------------
diff --git a/configuring/running/running_the_cacheserver.html.md.erb b/configuring/running/running_the_cacheserver.html.md.erb
index b68e417..9de1189 100644
--- a/configuring/running/running_the_cacheserver.html.md.erb
+++ b/configuring/running/running_the_cacheserver.html.md.erb
@@ -8,7 +8,7 @@ A Geode server is a process that runs as a long-lived, configurable member of a
The Geode server is used primarily for hosting long-lived data regions and for running standard Geode processes such as the server in a client/server configuration. You can start and stop servers using the following methods:
- The `gfsh` tool allows you to manage Geode server processes from the command line.
-- You can also start, stop and manage the Geode servers through the `com.gemstone.gemfire.distributed.ServerLauncher` API. The `ServerLauncher` API can only be used for Geode Servers that were started with `gfsh` or with the `ServerLauncher` class itself. See the JavaDocs for additional specifics on using the `ServerLauncher` API.
+- You can also start, stop and manage the Geode servers through the `org.apache.geode.distributed.ServerLauncher` API. The `ServerLauncher` API can only be used for Geode Servers that were started with `gfsh` or with the `ServerLauncher` class itself. See the JavaDocs for additional specifics on using the `ServerLauncher` API.
## <a id="running_the_cacheserver__section_E15FB1B039CE4F6CB2E4B5618D7ECAA1" class="no-quick-link"></a>Default Server Configuration and Log Files
@@ -99,10 +99,10 @@ gfsh>start server --name=server3 \
## Start the Server Programmatically
-Use `com.gemstone.gemfire.distributed.ServerLauncher` API to start the cache server process inside your code. Use the `ServerLauncher.Builder` class to construct an instance of the `ServerLauncher`, and then use the `start()` method to start the server service. The other methods in the `ServerLauncher` class provide status information about the server and allow you to stop the server.
+Use `org.apache.geode.distributed.ServerLauncher` API to start the cache server process inside your code. Use the `ServerLauncher.Builder` class to construct an instance of the `ServerLauncher`, and then use the `start()` method to start the server service. The other methods in the `ServerLauncher` class provide status information about the server and allow you to stop the server.
``` pre
-import com.gemstone.gemfire.distributed.ServerLauncher;
+import org.apache.geode.distributed.ServerLauncher;
public class MyEmbeddedServer {
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/configuring/running/running_the_locator.html.md.erb
----------------------------------------------------------------------
diff --git a/configuring/running/running_the_locator.html.md.erb b/configuring/running/running_the_locator.html.md.erb
index 0cd36ae..64ac02e 100644
--- a/configuring/running/running_the_locator.html.md.erb
+++ b/configuring/running/running_the_locator.html.md.erb
@@ -59,12 +59,12 @@ Use the following guidelines to start the locator:
gfsh> start locator --name=locator2 --bind-address=192.0.2.0 --port=13489
```
- - Start the locator using the `main` method in the `com.gemstone.gemfire.distributed.LocatorLauncher` class and the Java executable. For example:
+ - Start the locator using the `main` method in the `org.apache.geode.distributed.LocatorLauncher` class and the Java executable. For example:
``` pre
working/directory/of/Locator/process$java -server \
-classpath "$GEMFIRE/lib/locator-dependencies.jar:/path/to/application/classes.jar" \
- com.gemstone.gemfire.distributed.LocatorLauncher start Locator1 --port=11235 \
+ org.apache.geode.distributed.LocatorLauncher start Locator1 --port=11235 \
--redirect-output
```
@@ -87,10 +87,10 @@ Use the following guidelines to start the locator:
start-locator=13489
```
- - Use `com.gemstone.gemfire.distributed.LocatorLauncher` API to start the locator inside your code. Use the `LocatorLauncher.Builder` class to construct an instance of the `LocatorLauncher`, and then use the `start()` method to start a Locator service embedded in your Java application process. The other methods in the `LocatorLauncher` class provide status information about the locator and allow you to stop the locator.
+ - Use `org.apache.geode.distributed.LocatorLauncher` API to start the locator inside your code. Use the `LocatorLauncher.Builder` class to construct an instance of the `LocatorLauncher`, and then use the `start()` method to start a Locator service embedded in your Java application process. The other methods in the `LocatorLauncher` class provide status information about the locator and allow you to stop the locator.
``` pre
- import com.gemstone.gemfire.distributed.LocatorLauncher;
+ import org.apache.geode.distributed.LocatorLauncher;
public class MyEmbeddedLocator {
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/continuous_querying/implementing_continuous_querying.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/continuous_querying/implementing_continuous_querying.html.md.erb b/developing/continuous_querying/implementing_continuous_querying.html.md.erb
index 6414383..de4c81e 100644
--- a/developing/continuous_querying/implementing_continuous_querying.html.md.erb
+++ b/developing/continuous_querying/implementing_continuous_querying.html.md.erb
@@ -38,7 +38,7 @@ Before you begin, you should be familiar with [Querying](../querying_basics/chap
```
3. Write your CQ listeners to handle CQ events from the server.
- Implement `com.gemstone.gemfire.cache.query.CqListener` in each event handler you need. In addition to your main CQ listeners, you might have listeners that you use for all CQs to track statistics or other general information.
+ Implement `org.apache.geode.cache.query.CqListener` in each event handler you need. In addition to your main CQ listeners, you might have listeners that you use for all CQs to track statistics or other general information.
**Note:**
Be especially careful if you choose to update your cache from your `CqListener`. If your listener updates the region that is queried in its own CQ and that region has a `Pool` named, the update will be forwarded to the server. If the update on the server satisfies the same CQ, it may be returned to the same listener that did the update, which could put your application into an infinite loop. This same scenario could be played out with multiple regions and multiple CQs, if the listeners are programmed to update each other's regions.
@@ -51,7 +51,7 @@ Before you begin, you should be familiar with [Querying](../querying_basics/chap
{
public void onEvent(CqEvent cqEvent)
{
- // com.gemstone.gemfire.cache Operation associated with the query op
+ // org.apache.geode.cache Operation associated with the query op
Operation queryOperation = cqEvent.getQueryOperation();
// key and new value from the event
Object key = cqEvent.getKey();
@@ -92,7 +92,7 @@ Before you begin, you should be familiar with [Querying](../querying_basics/chap
{
public void onEvent(CqEvent cqEvent)
{
- // com.gemstone.gemfire.cache Operation associated with the query op
+ // org.apache.geode.cache Operation associated with the query op
Operation queryOperation = cqEvent.getQueryOperation();
// key and new value from the event
Object key = cqEvent.getKey();
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/data_serialization/auto_serialization.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/data_serialization/auto_serialization.html.md.erb b/developing/data_serialization/auto_serialization.html.md.erb
index 6002229..7e3dfa2 100644
--- a/developing/data_serialization/auto_serialization.html.md.erb
+++ b/developing/data_serialization/auto_serialization.html.md.erb
@@ -46,7 +46,7 @@ In your application where you manage data from the cache, provide the following
<pdx>
<pdx-serializer>
<class-name>
- com.gemstone.gemfire.pdx.ReflectionBasedAutoSerializer
+ org.apache.geode.pdx.ReflectionBasedAutoSerializer
</class-name>
<parameter name="classes">
<string>com.company.domain.DomainObject</string>
@@ -87,7 +87,7 @@ In your application where you manage data from the cache, provide the following
<pdx>
<pdx-serializer>
<class-name>
- com.gemstone.gemfire.pdx.ReflectionBasedAutoSerializer
+ org.apache.geode.pdx.ReflectionBasedAutoSerializer
</class-name>
<parameter name="classes">
<string>com.company.domain.DomainObject</string>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb b/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
index 9440b0a..59ceb3c 100644
--- a/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
+++ b/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
@@ -26,4 +26,4 @@ After executing a Geode query or calling `region.get`, you can use the following
- `toJSON`. Reads a PdxInstance and returns a JSON string.
- `toJSONByteArray`. Reads a PdxInstance and returns a JSON byte array.
-For more information on using the JSONFormatter, see the Java API documentation for `com.gemstone.gemfire.pdx.JSONFormatter`.
+For more information on using the JSONFormatter, see the Java API documentation for `org.apache.geode.pdx.JSONFormatter`.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/data_serialization/use_pdx_serializable.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/data_serialization/use_pdx_serializable.html.md.erb b/developing/data_serialization/use_pdx_serializable.html.md.erb
index d4aa2e7..948112b 100644
--- a/developing/data_serialization/use_pdx_serializable.html.md.erb
+++ b/developing/data_serialization/use_pdx_serializable.html.md.erb
@@ -7,14 +7,14 @@ For a domain object with source that you can modify, implement the `PdxSerializa
<a id="use_pdx_serializable__section_7F357A8E56B54BFB9A5778C0F89E034E"></a>
**Procedure**
-1. In your domain class, implement `PdxSerializable`, importing the required `com.gemstone.gemfire.pdx` classes.
+1. In your domain class, implement `PdxSerializable`, importing the required `org.apache.geode.pdx` classes.
For example:
``` pre
- import com.gemstone.gemfire.pdx.PdxReader;
- import com.gemstone.gemfire.pdx.PdxSerializable;
- import com.gemstone.gemfire.pdx.PdxWriter;
+ import org.apache.geode.pdx.PdxReader;
+ import org.apache.geode.pdx.PdxSerializable;
+ import org.apache.geode.pdx.PdxWriter;
public class PortfolioPdx implements PdxSerializable {
...
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/data_serialization/use_pdx_serializer.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/data_serialization/use_pdx_serializer.html.md.erb b/developing/data_serialization/use_pdx_serializer.html.md.erb
index 3cdf599..7ef401e 100644
--- a/developing/data_serialization/use_pdx_serializer.html.md.erb
+++ b/developing/data_serialization/use_pdx_serializer.html.md.erb
@@ -25,10 +25,10 @@ The `PdxSerializer` `toData` and `fromData` methods differ from those for `PdxSe
Example:
``` pre
- import com.gemstone.gemfire.cache.Declarable;
- import com.gemstone.gemfire.pdx.PdxReader;
- import com.gemstone.gemfire.pdx.PdxSerializer;
- import com.gemstone.gemfire.pdx.PdxWriter;
+ import org.apache.geode.cache.Declarable;
+ import org.apache.geode.pdx.PdxReader;
+ import org.apache.geode.pdx.PdxSerializer;
+ import org.apache.geode.pdx.PdxWriter;
public class ExamplePdxSerializer implements PdxSerializer, Declarable {
...
@@ -59,7 +59,7 @@ The `PdxSerializer` `toData` and `fromData` methods differ from those for `PdxSe
```
**Note:**
- You cannot specify a custom `pdx-serializer` class using gfsh, however the `configure pdx` command automatically configures the <span class="keyword apiname">com.gemstone.gemfire.pdx.ReflectionBasedAutoSerializer</span> class. See [configure pdx](../../tools_modules/gfsh/command-pages/configure.html#topic_jdkdiqbgphqh).
+ You cannot specify a custom `pdx-serializer` class using gfsh, however the `configure pdx` command automatically configures the <span class="keyword apiname">org.apache.geode.pdx.ReflectionBasedAutoSerializer</span> class. See [configure pdx](../../tools_modules/gfsh/command-pages/configure.html#topic_jdkdiqbgphqh).
3. Program `PdxSerializer.toData` to recognize, cast, and handle your domain object:
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/delta_propagation/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/delta_propagation/chapter_overview.html.md.erb b/developing/delta_propagation/chapter_overview.html.md.erb
index 6079292..1beb847 100644
--- a/developing/delta_propagation/chapter_overview.html.md.erb
+++ b/developing/delta_propagation/chapter_overview.html.md.erb
@@ -4,27 +4,27 @@ title: Delta Propagation
Delta propagation allows you to reduce the amount of data you send over the network by including only changes to objects rather than the entire object.
-- **[How Delta Propagation Works](../../developing/delta_propagation/how_delta_propagation_works.html)**
+- **[How Delta Propagation Works](how_delta_propagation_works.html)**
Delta propagation reduces the amount of data you send over the network. You do this by only sending the change, or delta, information about an object, instead of sending the entire changed object. If you do not use cloning when applying the deltas, you can also expect to generate less garbage in your receiving JVMs.
-- **[When to Avoid Delta Propagation](../../developing/delta_propagation/when_to_use_delta_prop.html)**
+- **[When to Avoid Delta Propagation](when_to_use_delta_prop.html)**
Generally, the larger your objects and the smaller the deltas, the greater the benefits of using delta propagation. Partitioned regions with higher redundancy levels generally benefit more from delta propagation. However, in some application scenarios, delta propagation does not show any significant benefits. On occasion it results in performance degradation.
-- **[Delta Propagation Properties](../../developing/delta_propagation/delta_propagation_properties.html)**
+- **[Delta Propagation Properties](delta_propagation_properties.html)**
This topic describes the properties that can be used to configure delta propagation.
-- **[Implementing Delta Propagation](../../developing/delta_propagation/implementing_delta_propagation.html)**
+- **[Implementing Delta Propagation](implementing_delta_propagation.html)**
- By default, delta propagation is enabled in your distributed system. When enabled, delta propagation is used for objects that implement `com.gemstone.gemfire.Delta`. You program the methods to store and extract delta information for your entries and to apply received delta information.
+ By default, delta propagation is enabled in your distributed system. When enabled, delta propagation is used for objects that implement `org.apache.geode.Delta`. You program the methods to store and extract delta information for your entries and to apply received delta information.
-- **[Errors In Delta Propagation](../../developing/delta_propagation/errors_in_delta_propagation.html)**
+- **[Errors In Delta Propagation](errors_in_delta_propagation.html)**
This topic lists the errors that can occur when using delta propagation.
-- **[Delta Propagation Example](../../developing/delta_propagation/delta_propagation_example.html)**
+- **[Delta Propagation Example](delta_propagation_example.html)**
This topic provides an example of delta propagation.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/delta_propagation/delta_propagation_example.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/delta_propagation/delta_propagation_example.html.md.erb b/developing/delta_propagation/delta_propagation_example.html.md.erb
index b541e06..075b32e 100644
--- a/developing/delta_propagation/delta_propagation_example.html.md.erb
+++ b/developing/delta_propagation/delta_propagation_example.html.md.erb
@@ -22,8 +22,8 @@ This example shows the basic approach to programming a `Delta` implementation.
``` pre
package delta;
-import com.gemstone.gemfire.Delta;
-import com.gemstone.gemfire.InvalidDeltaException;
+import org.apache.geode.Delta;
+import org.apache.geode.InvalidDeltaException;
import java.io.DataInput;
import java.io.DataOutput;
import java.io.IOException;
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/delta_propagation/implementing_delta_propagation.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/delta_propagation/implementing_delta_propagation.html.md.erb b/developing/delta_propagation/implementing_delta_propagation.html.md.erb
index 8a8a0a0..7727532 100644
--- a/developing/delta_propagation/implementing_delta_propagation.html.md.erb
+++ b/developing/delta_propagation/implementing_delta_propagation.html.md.erb
@@ -2,7 +2,7 @@
title: Implementing Delta Propagation
---
-By default, delta propagation is enabled in your distributed system. When enabled, delta propagation is used for objects that implement `com.gemstone.gemfire.Delta`. You program the methods to store and extract delta information for your entries and to apply received delta information.
+By default, delta propagation is enabled in your distributed system. When enabled, delta propagation is used for objects that implement `org.apache.geode.Delta`. You program the methods to store and extract delta information for your entries and to apply received delta information.
<a id="implementing_delta_propagation__section_877AC61D691C44078A782683F90D169B"></a>
Use the following procedure to implement delta propagation in your distributed system.
@@ -10,7 +10,7 @@ Use the following procedure to implement delta propagation in your distributed s
1. Study your object types and expected application behavior to determine which regions can benefit from using delta propagation. Delta propagation does not improve performance for all data and data modification scenarios. See [When to Avoid Delta Propagation](when_to_use_delta_prop.html#when_to_use_delta_prop).
2. For each region where you are using delta propagation, choose whether to enable cloning using the delta propagation property `cloning-enabled`. Cloning is disabled by default. See [Delta Propagation Properties](delta_propagation_properties.html#delta_propagation_properties).
3. If you do not enable cloning, review all associated listener code for dependencies on `EntryEvent.getOldValue`. Without cloning, Geode modifies the entry in place and so loses its reference to the old value. For delta events, the `EntryEvent` methods `getOldValue` and `getNewValue` both return the new value.
-4. For every class where you want delta propagation, implement `com.gemstone.gemfire.Delta` and update your methods to support delta propagation. Exactly how you do this depends on your application and object needs, but these steps describe the basic approach:
+4. For every class where you want delta propagation, implement `org.apache.geode.Delta` and update your methods to support delta propagation. Exactly how you do this depends on your application and object needs, but these steps describe the basic approach:
1. If the class is a plain old Java object (POJO), wrap it for this implementation and update your code to work with the wrapper class.
2. Define as transient any extra object fields that you use to manage delta state. This can help performance when the full object is distributed. Whenever standard Java serialization is used, the transient keyword indicates to Java to not serialize the field.
3. Study the object contents to decide how to handle delta changes. Delta propagation has the same issues of distributed concurrency control as the distribution of full objects, but on a more detailed level. Some parts of your objects may be able to change independent of one another while others may always need to change together. Send deltas large enough to keep your data logically consistent. If, for example, field A and field B depend on each other, then your delta distributions should either update both fields or neither. As with regular updates, the fewer producers you have on a data region, the lower your likelihood of concurrency issues.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/distributed_regions/how_distribution_works.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/distributed_regions/how_distribution_works.html.md.erb b/developing/distributed_regions/how_distribution_works.html.md.erb
index 65092f7..bbc7522 100644
--- a/developing/distributed_regions/how_distribution_works.html.md.erb
+++ b/developing/distributed_regions/how_distribution_works.html.md.erb
@@ -6,7 +6,7 @@ To use distributed and replicated regions, you should understand how they work a
<a id="how_distribution_works__section_2F892A4987C547E68CA78067133C2C2C"></a>
**Note:**
-The management of replicated and distributed regions supplements the general information for managing data regions provided in [Basic Configuration and Programming](../../basic_config/book_intro.html). See also `com.gemstone.gemfire.cache.PartitionAttributes`.
+The management of replicated and distributed regions supplements the general information for managing data regions provided in [Basic Configuration and Programming](../../basic_config/book_intro.html). See also `org.apache.geode.cache.PartitionAttributes`.
A distributed region automatically sends entry value updates to remote caches and receives updates from them.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/distributed_regions/locking_in_global_regions.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/distributed_regions/locking_in_global_regions.html.md.erb b/developing/distributed_regions/locking_in_global_regions.html.md.erb
index 9974c6c..6a6e030 100644
--- a/developing/distributed_regions/locking_in_global_regions.html.md.erb
+++ b/developing/distributed_regions/locking_in_global_regions.html.md.erb
@@ -10,10 +10,10 @@ In regions with global scope, locking helps ensure cache consistency.
Locking of regions and entries is done in two ways:
1. **Implicit**. Geode automatically locks global regions and their data entries during most operations. Region invalidation and destruction do not acquire locks.
-2. **Explicit**. You can use the API to explicitly lock the region and its entries. Do this to guarantee atomicity in tasks with multi-step distributed operations. The `Region` methods `com.gemstone.gemfire.cache.Region.getDistributedLock` and `com.gemstone.gemfire.cache.Region.getRegionDistributedLock` return instances of `java.util.concurrent.locks.Lock` for a region and a specified key.
+2. **Explicit**. You can use the API to explicitly lock the region and its entries. Do this to guarantee atomicity in tasks with multi-step distributed operations. The `Region` methods `org.apache.geode.cache.Region.getDistributedLock` and `org.apache.geode.cache.Region.getRegionDistributedLock` return instances of `java.util.concurrent.locks.Lock` for a region and a specified key.
**Note:**
- You must use the `Region` API to lock regions and region entries. Do not use the `DistributedLockService` in the `com.gemstone.gemfire.distributed` package. That service is available only for locking in arbitrary distributed applications. It is not compatible with the `Region` locking methods.
+ You must use the `Region` API to lock regions and region entries. Do not use the `DistributedLockService` in the `org.apache.geode.distributed` package. That service is available only for locking in arbitrary distributed applications. It is not compatible with the `Region` locking methods.
## <a id="locking_in_global_regions__section_5B47F9C5C27A4B789A3498AC553BB1FB" class="no-quick-link"></a>Lock Timeouts
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/distributed_regions/managing_distributed_regions.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/distributed_regions/managing_distributed_regions.html.md.erb b/developing/distributed_regions/managing_distributed_regions.html.md.erb
index 2dd1f73..f36d8ca 100644
--- a/developing/distributed_regions/managing_distributed_regions.html.md.erb
+++ b/developing/distributed_regions/managing_distributed_regions.html.md.erb
@@ -7,7 +7,7 @@ Plan the configuration and ongoing management of your distributed, replicated, a
<a id="configure_distributed_region__section_11E9E1B3EB5845D9A4FB226A992B8D0D"></a>
Before you begin, understand [Basic Configuration and Programming](../../basic_config/book_intro.html).
-1. Choose the region shortcut setting that most closely matches your region configuration. See **`com.gemstone.gemfire.cache.RegionShortcut`** or [Region Shortcuts](../../reference/topics/chapter_overview_regionshortcuts.html#concept_ymp_rkz_4dffhdfhk). To create a replicated region, use one of the `REPLICATE` shortcut settings. To create a preloaded region, set your region `data-policy` to `preloaded`. This `cache.xml` declaration creates a replicated region:
+1. Choose the region shortcut setting that most closely matches your region configuration. See **`org.apache.geode.cache.RegionShortcut`** or [Region Shortcuts](../../reference/topics/chapter_overview_regionshortcuts.html#concept_ymp_rkz_4dffhdfhk). To create a replicated region, use one of the `REPLICATE` shortcut settings. To create a preloaded region, set your region `data-policy` to `preloaded`. This `cache.xml` declaration creates a replicated region:
``` pre
<region-attributes refid="REPLICATE">
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/events/filtering_multisite_events.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/events/filtering_multisite_events.html.md.erb b/developing/events/filtering_multisite_events.html.md.erb
index 76086da..a46d18e 100644
--- a/developing/events/filtering_multisite_events.html.md.erb
+++ b/developing/events/filtering_multisite_events.html.md.erb
@@ -28,13 +28,13 @@ You install a `GatewayEventFilter` implementation to a configured gateway sender
<cache>
<gateway-sender id="remoteA" parallel="true" remote-distributed-system-id="1">
<gateway-event-filter>
- <class-name>com.gemstone.gemfire.util.SampleEventFilter</class-name>
+ <class-name>org.apache.geode.util.SampleEventFilter</class-name>
<parameter name="param1">
<string>"value1"</string>
</parameter>
</gateway-event-filter>
<gateway-transport-filter>
- <class-name>com.gemstone.gemfire.util.SampleTransportFilter</class-name>
+ <class-name>org.apache.geode.util.SampleTransportFilter</class-name>
<parameter name="param1">
<string>"value1"</string>
</parameter>
@@ -48,7 +48,7 @@ You install a `GatewayEventFilter` implementation to a configured gateway sender
...
<gateway-receiver start-port="1530" end-port="1551">
<gateway-transport-filter>
- <class-name>com.gemstone.gemfire.util.SampleTransportFilter</class-name>
+ <class-name>org.apache.geode.util.SampleTransportFilter</class-name>
<parameter name="param1">
<string>"value1"</string>
</parameter>
@@ -61,15 +61,15 @@ You install a `GatewayEventFilter` implementation to a configured gateway sender
``` pre
gfsh>create gateway-sender --id=remoteA --parallel=true --remote-distributed-id="1"
- --gateway-event-filter=com.gemstone.gemfire.util.SampleEventFilter
- --gateway-transport-filter=com.gemstone.gemfire.util.SampleTransportFilter
+ --gateway-event-filter=org.apache.geode.util.SampleEventFilter
+ --gateway-transport-filter=org.apache.geode.util.SampleTransportFilter
```
See [create gateway-sender](../../tools_modules/gfsh/command-pages/create.html#topic_hg2_bjz_ck).
``` pre
gfsh>create gateway-receiver --start-port=1530 --end-port=1551 \
- --gateway-transport-filter=com.gemstone.gemfire.util.SampleTransportFilter
+ --gateway-transport-filter=org.apache.geode.util.SampleTransportFilter
```
**Note:**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/events/implementing_cache_event_handlers.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/events/implementing_cache_event_handlers.html.md.erb b/developing/events/implementing_cache_event_handlers.html.md.erb
index 5473623..583fcdc 100644
--- a/developing/events/implementing_cache_event_handlers.html.md.erb
+++ b/developing/events/implementing_cache_event_handlers.html.md.erb
@@ -13,11 +13,11 @@ Write-behind cache listeners are created by extending the `AsyncEventListener` i
**Procedure**
1. Decide which events your application needs to handle. For each region, decide which events you want to handle. For the cache, decide whether to handle transaction events.
-2. For each event, decide which handlers to use. The `*Listener` and `*Adapter` classes in `com.gemstone.gemfire.cache.util` show the options.
+2. For each event, decide which handlers to use. The `*Listener` and `*Adapter` classes in `org.apache.geode.cache.util` show the options.
3. Program each event handler:
1. Extend the handler's adapter class.
- 2. If you want to declare the handler in the `cache.xml`, implement the `com.gemstone.gemfire.cache.Declarable` interface as well.
+ 2. If you want to declare the handler in the `cache.xml`, implement the `org.apache.geode.cache.Declarable` interface as well.
3. Implement the handler's callback methods as needed by your application.
**Note:**
@@ -27,9 +27,9 @@ Write-behind cache listeners are created by extending the `AsyncEventListener` i
``` pre
package myPackage;
- import com.gemstone.gemfire.cache.Declarable;
- import com.gemstone.gemfire.cache.EntryEvent;
- import com.gemstone.gemfire.cache.util.CacheListenerAdapter;
+ import org.apache.geode.cache.Declarable;
+ import org.apache.geode.cache.EntryEvent;
+ import org.apache.geode.cache.util.CacheListenerAdapter;
import java.util.Properties;
public class MyCacheListener extends CacheListenerAdapter implements Declarable {
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/events/list_of_event_handlers_and_events.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/events/list_of_event_handlers_and_events.html.md.erb b/developing/events/list_of_event_handlers_and_events.html.md.erb
index 7524d91..5f63db1 100644
--- a/developing/events/list_of_event_handlers_and_events.html.md.erb
+++ b/developing/events/list_of_event_handlers_and_events.html.md.erb
@@ -44,7 +44,7 @@ Use either cache handlers or membership handlers in any single application. Do n
</tr>
<tr>
<td><code class="ph codeph">ClientMembershipListener</code>
-<p>(com.gemstone.gemfire.management .membership.ClientMembershipListener)</p></td>
+<p>(org.apache.geode.management .membership.ClientMembershipListener)</p></td>
<td><code class="ph codeph">ClientMembershipEvent</code></td>
<td>One of the interfaces that replaces the deprecated Admin APIs. You can use the ClientMembershipListener to receive membership events only about clients. This listener's callback methods are invoked when this process detects connection changes to clients. Callback methods include <code class="ph codeph">memberCrashed</code>, <code class="ph codeph">memberJoined</code>, <code class="ph codeph">memberLeft</code> (graceful exit).</td>
</tr>
@@ -60,7 +60,7 @@ Use either cache handlers or membership handlers in any single application. Do n
</tr>
<tr>
<td><code class="ph codeph">MembershipListener</code>
-<p>(com.gemstone.gemfire.management .membership.MembershipListener)</p></td>
+<p>(org.apache.geode.management .membership.MembershipListener)</p></td>
<td><code class="ph codeph">MembershipEvent</code></td>
<td>Use this interface to receive membership events only about peers. This listener's callback methods are invoked when peer members join or leave the Geode distributed system. Callback methods include <code class="ph codeph">memberCrashed</code>, <code class="ph codeph">memberJoined</code>, and <code class="ph codeph">memberLeft</code> (graceful exit).</td>
</tr>
@@ -86,7 +86,7 @@ Extends <code class="ph codeph">CacheCallback</code> interface. Installed in cac
</tr>
<tr>
<td><code class="ph codeph">UniversalMembershipListenerAdapter</code>
-<p>(com.gemstone.gemfire .management.membership .UniversalMembershipListenerAdapter)</p></td>
+<p>(org.apache.geode .management.membership .UniversalMembershipListenerAdapter)</p></td>
<td><code class="ph codeph">MembershipEvent</code> and <code class="ph codeph">ClientMembershipEvent</code></td>
<td>One of the interfaces that replaces the deprecated Admin APIs. Provides a wrapper for MembershipListener and ClientMembershipListener callbacks for both clients and peers.</td>
</tr>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/events/resolving_multisite_conflicts.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/events/resolving_multisite_conflicts.html.md.erb b/developing/events/resolving_multisite_conflicts.html.md.erb
index eb06260..31fe7a3 100644
--- a/developing/events/resolving_multisite_conflicts.html.md.erb
+++ b/developing/events/resolving_multisite_conflicts.html.md.erb
@@ -17,7 +17,7 @@ A `GatewayConflictResolver` implementation is called only for update events that
1. Program the event handler:
1. Create a class that implements the `GatewayConflictResolver` interface.
- 2. If you want to declare the handler in `cache.xml`, implement the `com.gemstone.gemfire.cache.Declarable` interface as well.
+ 2. If you want to declare the handler in `cache.xml`, implement the `org.apache.geode.cache.Declarable` interface as well.
3. Implement the handler's `onEvent()` method to determine whether the WAN event should be allowed. `onEvent()` receives both a `TimestampedEntryEvent` and a `GatewayConflictHelper` instance. `TimestampedEntryEvent` has methods for obtaining the timestamp and distributed system ID of both the update event and the current region entry. Use methods in the `GatewayConflictHelper` to either disallow the update event (retaining the existing region entry value) or provide an alternate value.
**Example:**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/events/writing_callbacks_that_modify_the_cache.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/events/writing_callbacks_that_modify_the_cache.html.md.erb b/developing/events/writing_callbacks_that_modify_the_cache.html.md.erb
index 6ad9526..299fd87 100644
--- a/developing/events/writing_callbacks_that_modify_the_cache.html.md.erb
+++ b/developing/events/writing_callbacks_that_modify_the_cache.html.md.erb
@@ -34,10 +34,10 @@ public void afterCreate(EntryEvent event) {
try {
otherRegion.create(key, val);
}
- catch (com.gemstone.gemfire.cache.RegionDestroyedException e) {
+ catch (org.apache.geode.cache.RegionDestroyedException e) {
...
}
- catch (com.gemstone.gemfire.cache.EntryExistsException e) {
+ catch (org.apache.geode.cache.EntryExistsException e) {
...
}
}
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/eviction/configuring_data_eviction.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/eviction/configuring_data_eviction.html.md.erb b/developing/eviction/configuring_data_eviction.html.md.erb
index 9b13265..42f3dbd 100644
--- a/developing/eviction/configuring_data_eviction.html.md.erb
+++ b/developing/eviction/configuring_data_eviction.html.md.erb
@@ -19,7 +19,7 @@ Configure data eviction as follows. You do not need to perform these steps in th
- Overflow the entry data to disk. See [Persistence and Overflow](../storing_data_on_disk/chapter_overview.html).
3. Decide the maximum amount of data to allow in the member for the eviction measurement indicated. This is the maximum for all storage for the region in the member. For partitioned regions, this is the total for all buckets stored in the member for the region - including any secondary buckets used for redundancy.
-4. Decide whether to program a custom sizer for your region. If you are able to provide such a class, it might be faster than the standard sizing done by Geode. Your custom class must follow the guidelines for defining custom classes and, additionally, must implement `com.gemstone.gemfire.cache.util.ObjectSizer`. See [Requirements for Using Custom Classes in Data Caching](../../basic_config/data_entries_custom_classes/using_custom_classes.html).
+4. Decide whether to program a custom sizer for your region. If you are able to provide such a class, it might be faster than the standard sizing done by Geode. Your custom class must follow the guidelines for defining custom classes and, additionally, must implement `org.apache.geode.cache.util.ObjectSizer`. See [Requirements for Using Custom Classes in Data Caching](../../basic_config/data_entries_custom_classes/using_custom_classes.html).
**Note:**
You can also configure Regions using the gfsh command-line interface, however, you cannot configure `eviction-attributes` using gfsh. See [Region Commands](../../tools_modules/gfsh/quick_ref_commands_by_area.html#topic_EF03119A40EE492984F3B6248596E1DD) and [Disk Store Commands](../../tools_modules/gfsh/quick_ref_commands_by_area.html#topic_1ACC91B493EE446E89EC7DBFBBAE00EA).
@@ -48,7 +48,7 @@ Examples:
<partition-attributes local-max-memory="512" total-num-buckets="13"/>
<eviction-attributes>
<lru-memory-size action="local-destroy"/>
- <class-name>com.gemstone.gemfire.cache.util.ObjectSizer
+ <class-name>org.apache.geode.cache.util.ObjectSizer
</class-name>
</eviction-attributes>
</region-attributes>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/expiration/configuring_data_expiration.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/expiration/configuring_data_expiration.html.md.erb b/developing/expiration/configuring_data_expiration.html.md.erb
index 96c6a67..0fae74a 100644
--- a/developing/expiration/configuring_data_expiration.html.md.erb
+++ b/developing/expiration/configuring_data_expiration.html.md.erb
@@ -26,7 +26,7 @@ Configure the type of expiration and the expiration action to use.
```
- Override the region-wide settings for specific entries, if required by your application. To do this:
- 1. Program a custom expiration class that implements `com.gemstone.gemfire.cache.CustomExpiry`. Example:
+ 1. Program a custom expiration class that implements `org.apache.geode.cache.CustomExpiry`. Example:
``` pre
// Custom expiration class
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/function_exec/function_execution.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/function_exec/function_execution.html.md.erb b/developing/function_exec/function_execution.html.md.erb
index 6a7404e..8cb9f0e 100644
--- a/developing/function_exec/function_execution.html.md.erb
+++ b/developing/function_exec/function_execution.html.md.erb
@@ -14,7 +14,7 @@ Main tasks:
## <a id="function_execution__section_7D43B0C628D54F579D5C434D3DF69B3C" class="no-quick-link"></a>Write the Function Code
-To write the function code, you implement the `Function` interface or extend the `FunctionAdapter` class. Both are in the `com.gemstone.gemfire.cache.execute` package. The adapter class provides some default implementations for methods, which you can override.
+To write the function code, you implement the `Function` interface or extend the `FunctionAdapter` class. Both are in the `org.apache.geode.cache.execute` package. The adapter class provides some default implementations for methods, which you can override.
Code the methods you need for the function. These steps do not have to be done in this order.
@@ -52,10 +52,10 @@ import java.util.HashSet;
import java.util.Iterator;
import java.util.Set;
-import com.gemstone.gemfire.cache.execute.FunctionAdapter;
-import com.gemstone.gemfire.cache.execute.FunctionContext;
-import com.gemstone.gemfire.cache.execute.RegionFunctionContext;
-import com.gemstone.gemfire.cache.partition.PartitionRegionHelper;
+import org.apache.geode.cache.execute.FunctionAdapter;
+import org.apache.geode.cache.execute.FunctionContext;
+import org.apache.geode.cache.execute.RegionFunctionContext;
+import org.apache.geode.cache.partition.PartitionRegionHelper;
public class MultiGetFunction extends FunctionAdapter {
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/function_exec/how_function_execution_works.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/function_exec/how_function_execution_works.html.md.erb b/developing/function_exec/how_function_execution_works.html.md.erb
index 54608e8..19959e8 100644
--- a/developing/function_exec/how_function_execution_works.html.md.erb
+++ b/developing/function_exec/how_function_execution_works.html.md.erb
@@ -16,7 +16,7 @@ You can execute data-independent functions or data-dependent functions in Geode
- **On a region\u2014**If you are executing a data-dependent function, specify a region and, optionally, a set of keys on which to run the function. The method `FunctionService.onRegion()` directs a data-dependent function to execute on a specific region.
-See the `com.gemstone.gemfire.cache.execute.FunctionService` Java API documentation for more details.
+See the `org.apache.geode.cache.execute.FunctionService` Java API documentation for more details.
## <a id="how_function_execution_works__section_E0C4B7D2E4414F099788A5A441FF0E03" class="no-quick-link"></a>How Functions Are Executed
@@ -37,7 +37,7 @@ When a failure (such as an execution error or member crash while executing) occu
3. Calling the result collector\u2019s `clearResults` method
4. Executing the function
-For client regions, the system retries the execution according to `com.gemstone.gemfire.cache.client.Pool` `retryAttempts`. If the function fails to run every time, the final exception is returned to the `getResult` method.
+For client regions, the system retries the execution according to `org.apache.geode.cache.client.Pool` `retryAttempts`. If the function fails to run every time, the final exception is returned to the `getResult` method.
For member calls, the system retries until either it succeeds or no data remains in the system for the function to operate on.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/outside_data_sources/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/outside_data_sources/chapter_overview.html.md.erb b/developing/outside_data_sources/chapter_overview.html.md.erb
index 5953f31..fc4f5ac 100644
--- a/developing/outside_data_sources/chapter_overview.html.md.erb
+++ b/developing/outside_data_sources/chapter_overview.html.md.erb
@@ -7,7 +7,7 @@ Apache Geode has application plug-ins to read data into the cache and write it o
<a id="outside_data_sources__section_100B707BB812430E8D9CFDE3BE4698D1"></a>
The application plug-ins:
-1. Load data on cache misses using an implementation of a `com.gemstone.gemfire.cache.CacheLoader`. The `CacheLoader.load` method is called when the `get` operation can't find the value in the cache. The value returned from the loader is put into the cache and returned to the `get` operation. You might use this in conjunction with data expiration to get rid of old data, and your other data loading applications, which might be prompted by events in the outside data source. See [Configure Data Expiration](../expiration/configuring_data_expiration.html).
+1. Load data on cache misses using an implementation of a `org.apache.geode.cache.CacheLoader`. The `CacheLoader.load` method is called when the `get` operation can't find the value in the cache. The value returned from the loader is put into the cache and returned to the `get` operation. You might use this in conjunction with data expiration to get rid of old data, and your other data loading applications, which might be prompted by events in the outside data source. See [Configure Data Expiration](../expiration/configuring_data_expiration.html).
2. Write data out to the data source using the cache event handlers, `CacheWriter` and `CacheListener`. For implementation details, see [Implementing Cache Event Handlers](../events/implementing_cache_event_handlers.html).
- `CacheWriter` is run synchronously. Before performing any operation on a region entry, if any cache writers are defined for the region in the distributed system, the system invokes the most convenient writer. In partitioned and distributed regions, cache writers are usually defined in only a subset of the caches holding the region - often in only one cache. The cache writer can abort the region entry operation.
- `CacheListener` is run synchronously after the cache is updated. This listener works only on local cache events, so install your listener in every cache where you want it to handle events. You can install multiple cache listeners in any of your caches.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/outside_data_sources/implementing_data_loaders.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/outside_data_sources/implementing_data_loaders.html.md.erb b/developing/outside_data_sources/implementing_data_loaders.html.md.erb
index 155dfaf..2b65b44 100644
--- a/developing/outside_data_sources/implementing_data_loaders.html.md.erb
+++ b/developing/outside_data_sources/implementing_data_loaders.html.md.erb
@@ -11,9 +11,9 @@ To program a data loader and configure your region to use it:
## <a id="implementing_data_loaders__section_88076AF5EC184FE88AAF4C806A0CA9DF" class="no-quick-link"></a>Program your loader
To program your loader:
-1. Implement `com.gemstone.gemfire.cache.CacheLoader`.
+1. Implement `org.apache.geode.cache.CacheLoader`.
-2. If you want to declare the loader in your `cache.xml`, implement the `com.gemstone.gemfire.cache.Declarable` interface as well.
+2. If you want to declare the loader in your `cache.xml`, implement the `org.apache.geode.cache.Declarable` interface as well.
3. Program the single `CacheLoader` `load` method to do whatever your application requires for retrieving the value from outside the cache. If you need to run `Region` API calls from your loader, spawn separate threads for them. Do not make direct calls to `Region` methods from your load method implementation as it could cause the cache loader to block, hurting the performance of the distributed system. For example:
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/partitioned_regions/moving_partitioned_data.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/partitioned_regions/moving_partitioned_data.html.md.erb b/developing/partitioned_regions/moving_partitioned_data.html.md.erb
index 4632ac9..054f7fe 100644
--- a/developing/partitioned_regions/moving_partitioned_data.html.md.erb
+++ b/developing/partitioned_regions/moving_partitioned_data.html.md.erb
@@ -32,7 +32,7 @@ source = sourceMembers.iterator().next();
PartitionRegionHelper.moveBucketByKey(r, source, destination, product);
```
-See the Java API documentation for `com.gemstone.gemfire.cache.partition.PartitionRegionHelper.moveBucketByKey` for more details.
+See the Java API documentation for `org.apache.geode.cache.partition.PartitionRegionHelper.moveBucketByKey` for more details.
The `moveData` method moves data up to a given percentage (measured in bytes) from a source member to a destination member. For example, you could use this method to move a specified percentage of data from an overloaded member to another member to improve distribution.
@@ -52,7 +52,7 @@ DistributedMember destination = ds.findDistributedMember(destName);
PartitionRegionHelper.moveData(r, source, destination, 20);
```
-See the Java API documentation for `com.gemstone.gemfire.cache.partition.PartitionRegionHelper.moveData` for more details.
+See the Java API documentation for `org.apache.geode.cache.partition.PartitionRegionHelper.moveData` for more details.
For more information on partitioned regions and rebalancing, see [Partitioned Regions](chapter_overview.html).
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/partitioned_regions/using_custom_partition_resolvers.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/partitioned_regions/using_custom_partition_resolvers.html.md.erb b/developing/partitioned_regions/using_custom_partition_resolvers.html.md.erb
index 477ca2c..df9e4b3 100644
--- a/developing/partitioned_regions/using_custom_partition_resolvers.html.md.erb
+++ b/developing/partitioned_regions/using_custom_partition_resolvers.html.md.erb
@@ -10,7 +10,7 @@ If you are colocating data between regions and custom partitioning the data in t
<a id="custom_partition_region_data__section_1D7043815DF24308ABE4C78BFDFEE686"></a>
-For standard partitioning, use `com.gemstone.gemfire.cache.PartitionResolver`. To implement fixed partitioning, use `com.gemstone.gemfire.cache.FixedPartitionResolver`.
+For standard partitioning, use `org.apache.geode.cache.PartitionResolver`. To implement fixed partitioning, use `org.apache.geode.cache.FixedPartitionResolver`.
<a id="custom_partition_region_data__section_5A8D752F02834146A37D9430F1CA32DA"></a>
@@ -22,7 +22,7 @@ For standard partitioning, use `com.gemstone.gemfire.cache.PartitionResolver`. T
**Procedure**
-1. Using `com.gemstone.gemfire.cache.PartitionResolver` (standard partitioning) or `com.gemstone.gemfire.cache.FixedPartitionResolver` (fixed partitioning), implement the standard partitioning resolver or the fixed partitioning resolver in one of the following locations, listed here in the search order used by Geode:
+1. Using `org.apache.geode.cache.PartitionResolver` (standard partitioning) or `org.apache.geode.cache.FixedPartitionResolver` (fixed partitioning), implement the standard partitioning resolver or the fixed partitioning resolver in one of the following locations, listed here in the search order used by Geode:
- **Custom class**. You provide this class as the partition resolver to the region creation.
- **Entry key**. You use the implementing key object for every operation on the region entries.
- **Cache callback argument**. This implementation restricts you to using methods that accept a cache callback argument to manage the region entries. For a full list of the methods that take a callback argument, see the `Region` Javadocs.
@@ -57,7 +57,7 @@ For standard partitioning, use `com.gemstone.gemfire.cache.PartitionResolver`. T
4. For fixed partitioning only, program and configure additional fixed partitioning pieces:
1. Set the fixed partition attributes for each member.
- These attributes define the data stored for the region by the member and must be different for different members. See `com.gemstone.gemfire.cache.FixedPartitionAttributes` for definitions of the attributes. Define each `partition-name` in your data host members for the region. For each partition name, in the member you want to host the primary copy, define it with `is-primary` set to `true`. In every member you want to host the secondary copy, define it with `is-primary` set to `false` (the default). The number of secondaries must match the number of redundant copies you have defined for the region. See [Configure High Availability for a Partitioned Region](configuring_ha_for_pr.html).
+ These attributes define the data stored for the region by the member and must be different for different members. See `org.apache.geode.cache.FixedPartitionAttributes` for definitions of the attributes. Define each `partition-name` in your data host members for the region. For each partition name, in the member you want to host the primary copy, define it with `is-primary` set to `true`. In every member you want to host the secondary copy, define it with `is-primary` set to `false` (the default). The number of secondaries must match the number of redundant copies you have defined for the region. See [Configure High Availability for a Partitioned Region](configuring_ha_for_pr.html).
**Note:**
Buckets for a partition are hosted only by the members that have defined the partition name in their `FixedPartitionAttributes`.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/query_index/create_multiple_indexes.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/query_index/create_multiple_indexes.html.md.erb b/developing/query_index/create_multiple_indexes.html.md.erb
index a45f6d2..a629349 100644
--- a/developing/query_index/create_multiple_indexes.html.md.erb
+++ b/developing/query_index/create_multiple_indexes.html.md.erb
@@ -27,7 +27,7 @@ If index creation fails, you may receive an error message in gfsh similar to the
``` pre
gfsh>create defined indexes
-Exception : com.gemstone.gemfire.cache.query.RegionNotFoundException ,
+Exception : org.apache.geode.cache.query.RegionNotFoundException ,
Message : Region ' /r3' not found: from /r3Occurred on following members
1. india(s1:17866)<v1>:27809
```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/querying_basics/running_a_query.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/querying_basics/running_a_query.html.md.erb b/developing/querying_basics/running_a_query.html.md.erb
index cb213e4..c17dbed 100644
--- a/developing/querying_basics/running_a_query.html.md.erb
+++ b/developing/querying_basics/running_a_query.html.md.erb
@@ -9,7 +9,7 @@ The QueryService instance you should use depends on whether you are querying the
## <a id="running_a_querying__section_8B9C3F5BFBA6421A81EEB404DBE512C2" class="no-quick-link"></a>Querying a Local Cache
-To query the application's local cache or to query other members, use `com.gemstone.gemfire.cache.Cache.getQueryService`.
+To query the application's local cache or to query other members, use `org.apache.geode.cache.Cache.getQueryService`.
**Sample Code**
@@ -35,7 +35,7 @@ To query the application's local cache or to query other members, use `com.gemst
## <a id="running_a_querying__section_BAD35A249F784095857CC6848F91F6A4" class="no-quick-link"></a>Querying a Server Cache from a Client
-To perform a client to server query, use `com.gemstone.gemfire.cache.client.Pool.getQueryService`.
+To perform a client to server query, use `org.apache.geode.cache.client.Pool.getQueryService`.
**Sample Code**
[39/50] [abbrv] incubator-geode git commit: Preparing to update
gemfire links to geode [#130062377],
some preliminary corrections to existing text
Posted by rv...@apache.org.
Preparing to update gemfire links to geode [#130062377], some preliminary corrections to existing text
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/ebfed384
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/ebfed384
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/ebfed384
Branch: refs/staging/docs-grant1
Commit: ebfed384edcc99bb81f4688ee5b57a26bdd10d7d
Parents: a432d8e
Author: Dave Barnes <db...@pivotal.io>
Authored: Tue Sep 20 12:16:10 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Tue Sep 20 12:16:10 2016 -0700
----------------------------------------------------------------------
.../data_serialization/extending_the_autoserializer.html.md.erb | 2 +-
developing/function_exec/chapter_overview.html.md.erb | 5 +++--
developing/function_exec/function_execution.html.md.erb | 2 +-
3 files changed, 5 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ebfed384/developing/data_serialization/extending_the_autoserializer.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/data_serialization/extending_the_autoserializer.html.md.erb b/developing/data_serialization/extending_the_autoserializer.html.md.erb
index 3022221..8191787 100644
--- a/developing/data_serialization/extending_the_autoserializer.html.md.erb
+++ b/developing/data_serialization/extending_the_autoserializer.html.md.erb
@@ -27,7 +27,7 @@ You can customize the specific behaviors in `ReflectionBasedAutoSerializer` by o
These methods are only called the first time the `ReflectionBasedAutoSerializer` sees a new class. The results will be remembered and used the next time the same class is seen.
-For details on these methods and their default behaviors, see the JavaDocs on [ReflectionBasedAutoSerializer](/releases/latest/javadoc/com/gemstone/gemfire/pdx/ReflectionBasedAutoSerializer.html)for details.
+For details on these methods and their default behaviors, see the JavaDocs on [ReflectionBasedAutoSerializer](/releases/latest/javadoc/com/gemstone/gemfire/pdx/ReflectionBasedAutoSerializer.html) for details.
## <a id="concept_9E020566EE794A81A48A90BA798EC279__section_7C4CC39FD82A48A9B5F8376522078192" class="no-quick-link"></a>Example of Optimizing Autoserialization of BigInteger and BigDecimal Types
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ebfed384/developing/function_exec/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/function_exec/chapter_overview.html.md.erb b/developing/function_exec/chapter_overview.html.md.erb
index e9cf671..ead23a9 100644
--- a/developing/function_exec/chapter_overview.html.md.erb
+++ b/developing/function_exec/chapter_overview.html.md.erb
@@ -5,14 +5,15 @@ title: Function Execution
A function is a body of code that resides on a server and that an application can invoke from a client or from another server without the need to send the function code itself. The caller can direct a data-dependent function to operate on a particular dataset, or can direct a data-independent function to operate on a particular server, member, or member group.
<a id="function_exec__section_CBD5B04ACC554029B5C710CE8E244FEA">The function execution service provides solutions for a variety of use cases, including:</a>
+
- An application needs to perform an operation on the data associated with a key. A registered server-side function can retrieve the data, operate on it, and put it back, with all processing performed locally to the server.
- An application needs to initialize some of its components once on each server, which might be used later by executed functions.
- A third-party service, such as a messaging service, requires initialization and startup.
- Any arbitrary aggregation operation requires iteration over local data sets that can be done more efficiently through a single call to the cache server.
- An external resource needs provisioning that can be done by executing a function on a server.
-- **[How Function Execution Works](../../developing/function_exec/how_function_execution_works.html)**
+- **[How Function Execution Works](how_function_execution_works.html)**
-- **[Executing a Function in Apache Geode](../../developing/function_exec/function_execution.html)**
+- **[Executing a Function in Apache Geode](function_execution.html)**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ebfed384/developing/function_exec/function_execution.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/function_exec/function_execution.html.md.erb b/developing/function_exec/function_execution.html.md.erb
index 8cb9f0e..a881afd 100644
--- a/developing/function_exec/function_execution.html.md.erb
+++ b/developing/function_exec/function_execution.html.md.erb
@@ -40,7 +40,7 @@ Code the methods you need for the function. These steps do not have to be done i
**Note:**
When you use `PartitionRegionHelper.getLocalDataForContext`, `putIfAbsent` may not return expected results if you are working on local data set instead of the region.
- 4. To propagate an error condition or exception back to the caller of the function, throw a FunctionException from the `execute` method. Geode transmits the exception back to the caller as if it had been thrown on the calling side. See the Java API documentation for [FunctionException](/releases/latest/javadoc/com/gemstone/gemfire/cache/execute/FunctionException.html/) for more information.
+ 4. To propagate an error condition or exception back to the caller of the function, throw a FunctionException from the `execute` method. Geode transmits the exception back to the caller as if it had been thrown on the calling side. See the Java API documentation for [FunctionException](/releases/latest/javadoc/com/gemstone/gemfire/cache/execute/FunctionException.html) for more information.
Example function code:
[27/50] [abbrv] incubator-geode git commit: Rewrite the security
overview section [#130068769]
Posted by rv...@apache.org.
Rewrite the security overview section [#130068769]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/d4c43d36
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/d4c43d36
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/d4c43d36
Branch: refs/staging/docs-grant1
Commit: d4c43d36c9e107e1fd905b89d83d6ab2fbda9c57
Parents: 06b71c9
Author: Karen Miller <km...@pivotal.io>
Authored: Fri Sep 9 15:18:19 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Fri Sep 9 15:18:19 2016 -0700
----------------------------------------------------------------------
managing/security/chapter_overview.html.md.erb | 9 +-
.../security/implementing_security.html.md.erb | 92 ++++++++++----------
2 files changed, 46 insertions(+), 55 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/d4c43d36/managing/security/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/chapter_overview.html.md.erb b/managing/security/chapter_overview.html.md.erb
index 8b8ca63..88df5d8 100644
--- a/managing/security/chapter_overview.html.md.erb
+++ b/managing/security/chapter_overview.html.md.erb
@@ -4,14 +4,9 @@ title: Security
The security framework permits authentication of connecting components and authorization of operations for all communicating components of the distributed system.
-- **[Security Implementation Overview](../../managing/security/implementing_security.html)**
+- **[Security Implementation Introduction and Overview](../../managing/security/implementing_security.html)**
- Apache Geode can authenticate peer system members and clients. It can also authorize cache operations on a server from clients.
-
-- **[Security Features](../../managing/security/security_intro.html)**
-
- Encryption, SSL secure communication, authentication, and authorization
-features help to secure the distributed system.
+ Encryption, SSL secure communication, authentication, and authorization help to secure the distributed system.
- **[Security Detail Considerations](../../managing/security/security_audit_overview.html)**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/d4c43d36/managing/security/implementing_security.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_security.html.md.erb b/managing/security/implementing_security.html.md.erb
index b8122e5..4400af3 100644
--- a/managing/security/implementing_security.html.md.erb
+++ b/managing/security/implementing_security.html.md.erb
@@ -1,67 +1,63 @@
---
-title: Security Implementation Overview
+title: Security Implementation Introduction and Overview
---
-Apache Geode can authenticate system members, clients, and other system
-entities. It can also individually authorize cache operations
-for those various entities.
+## Security Features
+Encryption, SSL secure communication, authentication, and authorization
+features help to secure the distributed system.
-## <a id="implementing_security__section_79F6CF928E764CA294D466D0CB2E5FAC" class="no-quick-link"></a>An overview of How it all Works##
+Security features include:
-The security of a distributed system can be greatly enhanced by
-authenticating all system participants.
-This verifies the identity of the participants,
-gaining control over participation.
+- **A single security interface for all components**. The single
+authentication and authorization mechanism simplifies the security
+implementation.
+It views and interacts with all components in a consistent manner.
+- **System-wide role-based access control**.
+Roles regiment authorized operations requested by the various components.
+- **SSL communication**. Allows configuration of connections to be
+SSL-based, rather than plain socket connections.
+You can enable SSL separately for peer-to-peer, client, JMX, gateway senders and receivers, and HTTP connections.
+- **Post processing of region data**. Return values for operations that
+return region values may be altered, permitting the filtering of returned data.
+
+## Overview
+
+An authentication and authorization mechanism forms the core of
+the internal security of the distributed system.
+Communications may be further protected by enabling SSL for
+data in transit.
+
+Authentication verifies the identity of communicating components,
+leading to control over participation.
The variety of participants include peer members, cache servers,
clients, originators of JMX operations, Pulse,
-gateway receivers representing WAN members of the system,
+gateway senders and receivers representing WAN members of the system,
and commands arriving from `gfsh` on behalf of system users
or administrators.
+Connection requests trigger the invocation of an authentication
+callback.
+This special-purpose callback is written as part of the application,
+and it attempts to authenticate the requester by whatever
+algorithm it chooses.
+The result is either a returned principal representing the requester's
+authenticated identity or an exception indicating that the requester
+has not been authenticated.
+The principal becomes part of any request for operations,
+which go through the authorization process.
+
+
Given authentication,
isolation and access to cache data and system state can be further
-protected by implementing an authorization mechanism.
-For example, only certain system administrators might be permitted
+protected by implementing the authorization mechanism,
+also implemented as a special-purpose callback as part of the application.
+For example, the protection may be to permit only certain system administrators
to start and stop servers.
The authority to do this needs to be limited to specific
verified accounts, preventing those without the authorization.
-An implementation of an authorization mechanism requires
-that authenticated identities accompany all requests to the system,
+An implementation of the authorization callback will require
+that an authenticate identity accompanies all requests to the system,
and that the system maintains a representation of which identities
are permitted to complete which actions or cache commands.
-## Authentication and Authorization
-
-A single interface specifies authentication and a role-based access
-control for authorizing cache operations.
-
-Configuration in the form of property identifies the implementation
-of the interface.
-Defining the property enables the authentication/authorization defined
-in the implementation.
-
-A second property lists which components the implementation applies to.
-Therefore, it is configurable which components get authenticated and
-go through an authorization step prior to doing operations.
-
-## Access Control for Authorization
-
-The `ResourcePermission` object classifies operations.
-The two main parts of the object are the `Resource` and the `Operation`.
-The `Resource` identifies a role of a component within the
-distributed system.
-There are two roles:
-
-- `CLUSTER` is an administrative role.
-- `DATA` is a role that does operations on regions.
-
-The `Operation` qualifies what is to be accomplished.
-There are three values:
-
-- `READ` looks at data; it does not modify anything.
-- `WRITE` modifies data. `WRITE` does not imply `READ`.
-- `MANAGE` accesses administrative information. `MANAGE` does not imply `WRITE`.
-
-Data read and write operations may be further applied to regions
-and specific keys within regions.
[35/50] [abbrv] incubator-geode git commit: Complete the update of
setting credentials for authentication. [#130304427]
Posted by rv...@apache.org.
Complete the update of setting credentials for authentication.
[#130304427]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/b60f78a0
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/b60f78a0
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/b60f78a0
Branch: refs/staging/docs-grant1
Commit: b60f78a0758c174e63089886cb39e4090dd9a9b5
Parents: b9e16c0
Author: Karen Miller <km...@pivotal.io>
Authored: Thu Sep 15 13:37:42 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Thu Sep 15 13:37:42 2016 -0700
----------------------------------------------------------------------
.../implementing_authentication.html.md.erb | 20 ++++++++++++++------
1 file changed, 14 insertions(+), 6 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/b60f78a0/managing/security/implementing_authentication.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_authentication.html.md.erb b/managing/security/implementing_authentication.html.md.erb
index 98b5505..a605e1b 100644
--- a/managing/security/implementing_authentication.html.md.erb
+++ b/managing/security/implementing_authentication.html.md.erb
@@ -53,6 +53,11 @@ the properties `security-username` and `security-password` in whatever way
it wishes.
It might look up values in a database or another external resource.
+Gateway senders and receivers communicate as a component of their
+server member.
+Therefore, the credential of the server become those of the gateway
+sender or receiver.
+
## How a Cache Client Sets Its Credential
In order to connect with a locator or a server that does authentication,
@@ -65,7 +70,7 @@ There are two ways of accomplishing this:
as in the example
``` pre
- security-username=webclient
+ security-username=clientapp
security-password=xyz1234
```
The user name and password are stored in the clear, so the
@@ -88,13 +93,16 @@ or it might prompt for values.
## How Other Components Set Their Credentials
-gfsh prompts upon `gfsh connect`.
-
-Pulse prompts upon start up.
-
-Components connecting via the REST API do something.
+`gfsh` prompts for the user name and password upon invocation of
+a`gfsh connect` command.
+Pulse prompts for the user name and password upon start up.
+Due to the stateless nature of the REST API,
+a web application or other component that speaks to a server or locator
+via the REST API goes through authentication on each request.
+The header of the request needs to include attributes that define values for
+`security-username` and `security-password`.
## Implement SecurityManager Interface
[10/50] [abbrv] incubator-geode git commit: Fixed a positioning issue
in a link.
Posted by rv...@apache.org.
Fixed a positioning issue in a link.
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/51f43faf
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/51f43faf
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/51f43faf
Branch: refs/staging/docs-grant1
Commit: 51f43faf3bf77874336d93fe8ab15ceffb65dc26
Parents: 62a3bf9
Author: Dave Barnes <db...@pivotal.io>
Authored: Thu Sep 1 11:40:20 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Thu Sep 1 11:41:35 2016 -0700
----------------------------------------------------------------------
managing/security/security_audit_overview.html.md.erb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/51f43faf/managing/security/security_audit_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/security_audit_overview.html.md.erb b/managing/security/security_audit_overview.html.md.erb
index 13080c6..af2ea44 100644
--- a/managing/security/security_audit_overview.html.md.erb
+++ b/managing/security/security_audit_overview.html.md.erb
@@ -10,7 +10,7 @@ As part of this commitment, the following information is provided to help you se
Note that the intent of this section is to gather discrete pieces of information in one convenient location to better help you assess and configure the security of your environment.
-- **[External Interfaces, Ports, and Services](security-audit.html#topic_686158E9AFBD47518BE1B4BEB232C190)**
+- **[External Interfaces, Ports, and Services](security-audit.html)**
Geode processes use either UDP or TCP/IP ports to communicate with other processes or clients.
[12/50] [abbrv] incubator-geode git commit: Security - moved overview
to top of section.
Posted by rv...@apache.org.
Security - moved overview to top of section.
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/7c8acc58
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/7c8acc58
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/7c8acc58
Branch: refs/staging/docs-grant1
Commit: 7c8acc589fd57fb523109adf41a9198515b1a82c
Parents: bce4a11
Author: Dave Barnes <db...@pivotal.io>
Authored: Fri Sep 2 15:58:14 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Fri Sep 2 15:58:14 2016 -0700
----------------------------------------------------------------------
managing/security/chapter_overview.html.md.erb | 8 ++++----
managing/security/implementing_authentication.html.md.erb | 3 ++-
managing/security/implementing_security.html.md.erb | 9 +++++----
3 files changed, 11 insertions(+), 9 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/7c8acc58/managing/security/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/chapter_overview.html.md.erb b/managing/security/chapter_overview.html.md.erb
index d1636a3..8b8ca63 100644
--- a/managing/security/chapter_overview.html.md.erb
+++ b/managing/security/chapter_overview.html.md.erb
@@ -4,6 +4,10 @@ title: Security
The security framework permits authentication of connecting components and authorization of operations for all communicating components of the distributed system.
+- **[Security Implementation Overview](../../managing/security/implementing_security.html)**
+
+ Apache Geode can authenticate peer system members and clients. It can also authorize cache operations on a server from clients.
+
- **[Security Features](../../managing/security/security_intro.html)**
Encryption, SSL secure communication, authentication, and authorization
@@ -13,10 +17,6 @@ features help to secure the distributed system.
This section gathers discrete details in one convenient location to better help you assess and configure the security of your environment.
-- **[Security Implementation Overview](../../managing/security/implementing_security.html)**
-
- Apache Geode can authenticate peer system members and clients. It can also authorize cache operations on a server from clients.
-
- **[Enable Security with Property Definitions](../../managing/security/enable_security.html)**
- **[Authentication](../../managing/security/authentication_overview.html)**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/7c8acc58/managing/security/implementing_authentication.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_authentication.html.md.erb b/managing/security/implementing_authentication.html.md.erb
index 52c6114..e7ae1d1 100644
--- a/managing/security/implementing_authentication.html.md.erb
+++ b/managing/security/implementing_authentication.html.md.erb
@@ -15,9 +15,10 @@ If approved, the connection request returns a `java.security.Principal` object,
- Servers may be authenticated by their clients during the connection initialization.
- Depending on the member, the new member may in turn become an authenticator to other joining members. Members joining a system must trust that existing members are already authenticated.
-Locators maintain and distribute the authenticated member list. The distributed member list is also authenticated by all members, which prevents an unauthorized application from introducing itself into membership by distributing an member list that includes itself.
+Locators maintain and distribute the authenticated member list. The distributed member list is also authenticated by all members, which prevents an unauthorized application from introducing itself into membership by distributing a member list that includes itself.
<img src="../../images/security-1.gif" id="how_authentication_works__image_D3AE53AB4E0441A5A078E5D07EC20C5D" class="image" />
+
Geode authentication provides a flexible plug-in framework. Any security infrastructure can be plugged in to the system as long as the plug-ins implement the required Geode interfaces.
## Enable Authentication with Property Definitions
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/7c8acc58/managing/security/implementing_security.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_security.html.md.erb b/managing/security/implementing_security.html.md.erb
index e70712b..b8122e5 100644
--- a/managing/security/implementing_security.html.md.erb
+++ b/managing/security/implementing_security.html.md.erb
@@ -6,8 +6,9 @@ Apache Geode can authenticate system members, clients, and other system
entities. It can also individually authorize cache operations
for those various entities.
-<a id="implementing_security__section_79F6CF928E764CA294D466D0CB2E5FAC"></a>
-An overview of How it all Works
+
+## <a id="implementing_security__section_79F6CF928E764CA294D466D0CB2E5FAC" class="no-quick-link"></a>An overview of How it all Works##
+
The security of a distributed system can be greatly enhanced by
authenticating all system participants.
This verifies the identity of the participants,
@@ -20,7 +21,7 @@ or administrators.
Given authentication,
isolation and access to cache data and system state can be further
-protected by implementing a authorization mechanism.
+protected by implementing an authorization mechanism.
For example, only certain system administrators might be permitted
to start and stop servers.
The authority to do this needs to be limited to specific
@@ -60,7 +61,7 @@ There are three values:
- `READ` looks at data; it does not modify anything.
- `WRITE` modifies data. `WRITE` does not imply `READ`.
-- `MANAGE` accesses admininistrative information. `MANAGE` does not imply `WRITE`.
+- `MANAGE` accesses administrative information. `MANAGE` does not imply `WRITE`.
Data read and write operations may be further applied to regions
and specific keys within regions.
[37/50] [abbrv] incubator-geode git commit: Remove deprecated
properties jmx-manager-access-file and jmx-manager-password file.
[#128695663]
Posted by rv...@apache.org.
Remove deprecated properties jmx-manager-access-file and jmx-manager-password file. [#128695663]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/b7f30786
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/b7f30786
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/b7f30786
Branch: refs/staging/docs-grant1
Commit: b7f30786925c19063ede3b75212d685eb18229f6
Parents: e3196ed
Author: Dave Barnes <db...@pivotal.io>
Authored: Mon Sep 19 15:37:21 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Mon Sep 19 15:37:21 2016 -0700
----------------------------------------------------------------------
reference/topics/gemfire_properties.html.md.erb | 10 ----------
1 file changed, 10 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/b7f30786/reference/topics/gemfire_properties.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/gemfire_properties.html.md.erb b/reference/topics/gemfire_properties.html.md.erb
index b4726bf..06c72a2 100644
--- a/reference/topics/gemfire_properties.html.md.erb
+++ b/reference/topics/gemfire_properties.html.md.erb
@@ -182,11 +182,6 @@ See <a href="../../configuring/cluster_config/using_member_groups.html">Using Me
<td>If true then this member is willing to be a JMX Manager. All the other JMX Manager properties will be used when it does become a manager. If this property is false then all other <code class="ph codeph">jmx-manager-*</code> properties are ignored.</td>
<td>false (except on locators)</td>
</tr>
-<tr class="odd">
-<td>jmx-manager-access-file</td>
-<td>By default the JMX Manager will allow full access to all mbeans by any client. If this property is set to the name of a file then it can restrict clients to only being able to read MBeans; they will not be able to modify MBeans. The access level can be configured differently in this file for each user name defined in the password file. For more information about the format of this file see Oracle's documentation of the com.sun.management.jmxremote.access.file system property. Ignored if <code class="ph codeph">jmx-manager</code> is false or if <code class="ph codeph">jmx-manager-port</code> is zero.</td>
-<td><em>not set</em></td>
-</tr>
<tr class="even">
<td>jmx-manager-bind-address</td>
<td>By default the jmx-manager (when configured with a port) will listen on all the local host's addresses. You can use this property to configure what IP address or host name the JMX Manager will listen on for non-HTTP connections. Ignored if JMX Manager is false or <code class="ph codeph">jmx-manager-port</code> is zero.</td>
@@ -202,11 +197,6 @@ See <a href="../../configuring/cluster_config/using_member_groups.html">Using Me
<td><em>Deprecated.</em> Use <code class="ph codeph">http-service-port</code> instead.</td>
<td>7070</td>
</tr>
-<tr class="odd">
-<td>jmx-manager-password-file</td>
-<td>By default the JMX Manager will allow clients without credentials to connect. If this property is set to the name of a file then only clients that connect with credentials that match an entry in this file will be allowed. Most JVMs require that the file is only readable by the owner. For more information about the format of this file see Oracle's documentation of the com.sun.management.jmxremote.password.file system property. Ignored if <code class="ph codeph">jmx-manager</code> is false or if <code class="ph codeph">jmx-manager-port</code> is zero.</td>
-<td><em>not set</em></td>
-</tr>
<tr class="even">
<td>jmx-manager-port</td>
<td>The port this JMX Manager will listen to for client connections. If this property is set to zero then Geode will not allow remote client connections but you can alternatively use the standard system properties supported by the JVM for configuring access from remote JMX clients. Ignored if <code class="ph codeph">jmx-manager</code> is false.</td>
[24/50] [abbrv] incubator-geode git commit: GEODE-37 Package renaming
[#118023839]
Posted by rv...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/region_options/dynamic_region_creation.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/region_options/dynamic_region_creation.html.md.erb b/developing/region_options/dynamic_region_creation.html.md.erb
index a90eaae..2974f22 100644
--- a/developing/region_options/dynamic_region_creation.html.md.erb
+++ b/developing/region_options/dynamic_region_creation.html.md.erb
@@ -4,11 +4,11 @@ title: Creating Regions Dynamically
You can dynamically create regions in your application code and automatically instantiate them on members of a distributed system.
-If your application does not require partitioned regions, you can use the <span class="keyword apiname">com.gemstone.gemfire.cache.DynamicRegionFactory</span> class to dynamically create regions, or you can create them using the `<dynamic-region-factory>` element in the cache.xml file that defines the region. See [<dynamic-region-factory>](../../reference/topics/cache_xml.html#dynamic-region-factory).
+If your application does not require partitioned regions, you can use the <span class="keyword apiname">org.apache.geode.cache.DynamicRegionFactory</span> class to dynamically create regions, or you can create them using the `<dynamic-region-factory>` element in the cache.xml file that defines the region. See [<dynamic-region-factory>](../../reference/topics/cache_xml.html#dynamic-region-factory).
Due to the number of options involved, most developers use functions to create regions dynamically in their applications, as described in this topic. Dynamic regions can also be created from the `gfsh` command line.
-For a complete discussion of using Geode functions, see [Function Execution](../function_exec/chapter_overview.html). Functions use the <span class="keyword apiname">com.gemstone.gemfire.cache.execute.FunctionService</span> class.
+For a complete discussion of using Geode functions, see [Function Execution](../function_exec/chapter_overview.html). Functions use the <span class="keyword apiname">org.apache.geode.cache.execute.FunctionService</span> class.
For example, the following Java classes define and use a function for dynamic region creation:
@@ -17,17 +17,17 @@ The <span class="keyword apiname">CreateRegionFunction</span> class defines a fu
``` pre
#CreateRegionFunction.java
-import com.gemstone.gemfire.cache.Cache;
-import com.gemstone.gemfire.cache.CacheFactory;
-import com.gemstone.gemfire.cache.DataPolicy;
-import com.gemstone.gemfire.cache.Declarable;
-import com.gemstone.gemfire.cache.Region;
-import com.gemstone.gemfire.cache.RegionAttributes;
-import com.gemstone.gemfire.cache.RegionFactory;
-import com.gemstone.gemfire.cache.Scope;
+import org.apache.geode.cache.Cache;
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.cache.DataPolicy;
+import org.apache.geode.cache.Declarable;
+import org.apache.geode.cache.Region;
+import org.apache.geode.cache.RegionAttributes;
+import org.apache.geode.cache.RegionFactory;
+import org.apache.geode.cache.Scope;
-import com.gemstone.gemfire.cache.execute.Function;
-import com.gemstone.gemfire.cache.execute.FunctionContext;
+import org.apache.geode.cache.execute.Function;
+import org.apache.geode.cache.execute.FunctionContext;
import java.util.Properties;
@@ -120,16 +120,16 @@ The <span class="keyword apiname">CreateRegionCacheListener</span> class is a ca
``` pre
#CreateRegionCacheListener.java
-import com.gemstone.gemfire.cache.Cache;
-import com.gemstone.gemfire.cache.CacheFactory;
-import com.gemstone.gemfire.cache.Declarable;
-import com.gemstone.gemfire.cache.EntryEvent;
-import com.gemstone.gemfire.cache.Region;
-import com.gemstone.gemfire.cache.RegionAttributes;
-import com.gemstone.gemfire.cache.RegionEvent;
-import com.gemstone.gemfire.cache.RegionExistsException;
+import org.apache.geode.cache.Cache;
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.cache.Declarable;
+import org.apache.geode.cache.EntryEvent;
+import org.apache.geode.cache.Region;
+import org.apache.geode.cache.RegionAttributes;
+import org.apache.geode.cache.RegionEvent;
+import org.apache.geode.cache.RegionExistsException;
-import com.gemstone.gemfire.cache.util.CacheListenerAdapter;
+import org.apache.geode.cache.util.CacheListenerAdapter;
import java.util.Map;
import java.util.Properties;
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/storing_data_on_disk/storing_data_on_disk.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/storing_data_on_disk/storing_data_on_disk.html.md.erb b/developing/storing_data_on_disk/storing_data_on_disk.html.md.erb
index 5f6f065..9aefd7c 100644
--- a/developing/storing_data_on_disk/storing_data_on_disk.html.md.erb
+++ b/developing/storing_data_on_disk/storing_data_on_disk.html.md.erb
@@ -55,8 +55,8 @@ You can also configure Regions and Disk Stores using the gfsh command-line inter
| Related Topics |
|---------------------------------------------------------------------------------------|
-| `com.gemstone.gemfire.cache.RegionAttributes` for data region persistence information |
-| `com.gemstone.gemfire.cache.EvictionAttributes` for data region overflow information |
-| `com.gemstone.gemfire.cache.server.ClientSubscriptionConfig` |
+| `org.apache.geode.cache.RegionAttributes` for data region persistence information |
+| `org.apache.geode.cache.EvictionAttributes` for data region overflow information |
+| `org.apache.geode.cache.server.ClientSubscriptionConfig` |
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/transactions/JTA_transactions.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/transactions/JTA_transactions.html.md.erb b/developing/transactions/JTA_transactions.html.md.erb
index cbb303d..31d0cbb 100644
--- a/developing/transactions/JTA_transactions.html.md.erb
+++ b/developing/transactions/JTA_transactions.html.md.erb
@@ -198,7 +198,7 @@ To run a global transaction, perform the following steps:
3. Configure Geode for any necessary transactional behavior. Enable `copy-on-read` for your cache and specify a transaction listener, if you need one. See [Setting Global Copy on Read](working_with_transactions.html#concept_vx2_gs4_5k) and [Configuring Transaction Plug-In Event Handlers](working_with_transactions.html#concept_ocw_vf1_wk) for details.
4. Make sure that JTA transactions are not disabled in the `cache.xml` file or the application code.
5. Initialize the Geode cache.
-6. Get an initial context through `com.gemstone.gemfire.cache.Cache.getJNDIContext`. For example:
+6. Get an initial context through `org.apache.geode.cache.Cache.getJNDIContext`. For example:
``` pre
Context ctx = cache.getJNDIContext();
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/developing/transactions/transactional_function_example.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/transactions/transactional_function_example.html.md.erb b/developing/transactions/transactional_function_example.html.md.erb
index 7397b52..6539131 100644
--- a/developing/transactions/transactional_function_example.html.md.erb
+++ b/developing/transactions/transactional_function_example.html.md.erb
@@ -14,7 +14,7 @@ public class TransactionalFunction extends FunctionAdapter {
private Random random = new Random();
/* (non-Javadoc)
- * @see com.gemstone.gemfire.cache.execute.FunctionAdapter#execute(com.gemstone.gemfire.cache.execute.FunctionContext)
+ * @see org.apache.geode.cache.execute.FunctionAdapter#execute(org.apache.geode.cache.execute.FunctionContext)
*/
@Override
public void execute(FunctionContext context) {
@@ -42,7 +42,7 @@ public class TransactionalFunction extends FunctionAdapter {
}
/* (non-Javadoc)
- * @see com.gemstone.gemfire.cache.execute.FunctionAdapter#getId()
+ * @see org.apache.geode.cache.execute.FunctionAdapter#getId()
*/
@Override
public String getId() {
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/getting_started/querying_quick_reference.html.md.erb
----------------------------------------------------------------------
diff --git a/getting_started/querying_quick_reference.html.md.erb b/getting_started/querying_quick_reference.html.md.erb
index 7be742a..a4d051d 100644
--- a/getting_started/querying_quick_reference.html.md.erb
+++ b/getting_started/querying_quick_reference.html.md.erb
@@ -490,9 +490,9 @@ ELEMENT(SELECT DISTINCT * FROM /exampleRegion WHERE id = 'XYZ-1').status = 'acti
## <a id="reference_D5CE64F5FD6F4A808AEFB748C867189E__section_5383407F9D004D4EB4E695252EBA1EF0" class="no-quick-link"></a>Which APIs should I use to write my queries?
-If you are querying a Java application\u2019s local cache or querying other members, use [com.gemstone.gemfire.cache.Cache.getQueryService](/releases/latest/javadoc/com/gemstone/gemfire/cache/query/QueryService.html).
+If you are querying a Java application\u2019s local cache or querying other members, use [org.apache.geode.cache.Cache.getQueryService](/releases/latest/javadoc/com/gemstone/gemfire/cache/query/QueryService.html).
-If you are writing a Java client to server query, use [com.gemstone.gemfire.cache.client.Pool.getQueryService](/releases/latest/javadoc/com/gemstone/gemfire/cache/client/Pool.html).
+If you are writing a Java client to server query, use [org.apache.geode.cache.client.Pool.getQueryService](/releases/latest/javadoc/com/gemstone/gemfire/cache/client/Pool.html).
If you are writing a native client to server query, use the [.NET API](/releases/latest/net_api/DotNetDocs/Index.html) or the [C++ API](/releases/latest/cpp_api/cppdocs/index.html).
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/getting_started/setup_classpath.html.md.erb
----------------------------------------------------------------------
diff --git a/getting_started/setup_classpath.html.md.erb b/getting_started/setup_classpath.html.md.erb
index 0525b2c..c994d70 100644
--- a/getting_started/setup_classpath.html.md.erb
+++ b/getting_started/setup_classpath.html.md.erb
@@ -78,7 +78,7 @@ For example, to start up a Geode locator process using the LocatorLauncher API,
``` pre
prompt# java -cp "path_to_product/lib/geode-dependencies.jar"
-com.gemstone.gemfire.distributed.LocatorLauncher start locator1
+org.apache.geode.distributed.LocatorLauncher start locator1
<locator-launcher-options>
```
@@ -86,7 +86,7 @@ To start up a Geode server process using the ServerLauncher API:
``` pre
prompt# java -cp "path_to_product/lib/geode-dependencies.jar:/path/to/your/applications/classes.jar"
-com.gemstone.gemfire.distributed.ServerLauncher start server1
+org.apache.geode.distributed.ServerLauncher start server1
<server-launcher-options>
```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/disk_storage/disk_store_configuration_params.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/disk_storage/disk_store_configuration_params.html.md.erb b/managing/disk_storage/disk_store_configuration_params.html.md.erb
index 3cad1a7..53ad195 100644
--- a/managing/disk_storage/disk_store_configuration_params.html.md.erb
+++ b/managing/disk_storage/disk_store_configuration_params.html.md.erb
@@ -4,7 +4,7 @@ title: Disk Store Configuration Parameters
You define your disk stores by using the `gfsh create disk-store` command or in `<disk-store>` subelements of your cache declaration in `cache.xml`. All disk stores are available for use by all of your regions and queues.
-These `<disk-store>` attributes and subelements have corresponding `gfsh create disk-store` command-line parameters as well as getter and setter methods in the `com.gemstone.gemfire.cache.DiskStoreFactory` and `com.gemstone.gemfire.cache.DiskStore` APIs.
+These `<disk-store>` attributes and subelements have corresponding `gfsh create disk-store` command-line parameters as well as getter and setter methods in the `org.apache.geode.cache.DiskStoreFactory` and `org.apache.geode.cache.DiskStore` APIs.
## <a id="disk_store_configuration_params__section_77273B9B5EA54227A2D25682BD77BAC3" class="no-quick-link"></a>Disk Store Configuration Attributes and Elements
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/heap_use/heap_management.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/heap_use/heap_management.html.md.erb b/managing/heap_use/heap_management.html.md.erb
index 1227de4..f3b90b7 100644
--- a/managing/heap_use/heap_management.html.md.erb
+++ b/managing/heap_use/heap_management.html.md.erb
@@ -60,7 +60,7 @@ When heap use passes the eviction threshold in either direction, the manager log
When heap use exceeds the critical threshold, the manager logs an error-level message. Avoid exceeding the critical threshold. Once identified as critical, the Geode member becomes a read-only member that refuses cache updates for all of its regions, including incoming distributed updates.
-For more information, see `com.gemstone.gemfire.cache.control.ResourceManager` in the online API documentation.
+For more information, see `org.apache.geode.cache.control.ResourceManager` in the online API documentation.
## <a id="how_the_resource_manager_works__section_EA5E52E65923486488A71E3E6F0DE9DA" class="no-quick-link"></a>How Background Eviction Is Performed
@@ -97,7 +97,7 @@ For the members where you want to activate the resource manager:
## <a id="configuring_resource_manager__section_4949882892DA46F6BB8588FA97037F45" class="no-quick-link"></a>Configure Geode for Heap LRU Management
-The configuration terms used here are `cache.xml` elements and attributes, but you can also configure through `gfsh` and the `com.gemstone.gemfire.cache.control.ResourceManager` and `Region` APIs.
+The configuration terms used here are `cache.xml` elements and attributes, but you can also configure through `gfsh` and the `org.apache.geode.cache.control.ResourceManager` and `Region` APIs.
1. When starting up your server, set `initial-heap` and `max-heap` to the same value.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/heap_use/off_heap_management.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/heap_use/off_heap_management.html.md.erb b/managing/heap_use/off_heap_management.html.md.erb
index 13b472d..0c8bf7c 100644
--- a/managing/heap_use/off_heap_management.html.md.erb
+++ b/managing/heap_use/off_heap_management.html.md.erb
@@ -118,7 +118,7 @@ supports off-heap options `--lock-memory`, `\u2011\u2011off-heap-memory-size`, `\u2011\u2011
## ResourceManager API
-The `com.gemstone.gemfire.cache.control.ResourceManager` interface defines methods that support off-heap use:
+The `org.apache.geode.cache.control.ResourceManager` interface defines methods that support off-heap use:
- `public void setCriticalOffHeapPercentage(float Percentage)`
- `public float getCriticalOffHeapPercentage()`
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/logging/logging_categories.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/logging/logging_categories.html.md.erb b/managing/logging/logging_categories.html.md.erb
index d259962..f22a23d 100644
--- a/managing/logging/logging_categories.html.md.erb
+++ b/managing/logging/logging_categories.html.md.erb
@@ -137,11 +137,11 @@ These are the levels, in descending order, with sample output:
``` pre
[warning 2008/06/09 13:12:31.833 PDT <main> tid=0x1] Unable to create a
connection in the allowed time
- com.gemstone.gemfire.cache.client.NoAvailableServersException
- at com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl.
+ org.apache.geode.cache.client.NoAvailableServersException
+ at org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.
borrowConnection(ConnectionManagerImpl.java:166)
. . .
- com.gemstone.gemfire.internal.cache.LocalRegion.get(LocalRegion.java:1122
+ org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1122
)
```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/logging/logging_whats_next.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/logging/logging_whats_next.html.md.erb b/managing/logging/logging_whats_next.html.md.erb
index d80309e..4ffda14 100644
--- a/managing/logging/logging_whats_next.html.md.erb
+++ b/managing/logging/logging_whats_next.html.md.erb
@@ -36,4 +36,4 @@ Search for lines that begin with these strings:
## <a id="logging_whats_next__section_32F26033A2134525BCC10F3A6C6FAD7B" class="no-quick-link"></a>Creating Your Own Log Messages
-In addition to the system logs, you can add your own application logs from your Java code. For information on adding custom logging to your applications, see the online Java documentation for the `com.gemstone.gemfire.LogWriter` interface. Both system and application logging is output and stored according to your logging configuration settings.
+In addition to the system logs, you can add your own application logs from your Java code. For information on adding custom logging to your applications, see the online Java documentation for the `org.apache.geode.LogWriter` interface. Both system and application logging is output and stored according to your logging configuration settings.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/management/list_of_mbeans_full.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/management/list_of_mbeans_full.html.md.erb b/managing/management/list_of_mbeans_full.html.md.erb
index 007e631..74fb2bd 100644
--- a/managing/management/list_of_mbeans_full.html.md.erb
+++ b/managing/management/list_of_mbeans_full.html.md.erb
@@ -29,7 +29,7 @@ You must configure the node to allow it to become a JMX Manager. See [Configurin
| Object Name | GemFire:type=Member, service=Manager,member=<name-or-dist-member-id> |
| Instances Per Node | 1 |
-See the `com.gemstone.gemfire.management.ManagerMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.ManagerMXBean` JavaDocs for information on available MBean methods and attributes.
## <a id="topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_4D7A4C82DD974BB5A5E52B34A6D888B4" class="no-quick-link"></a>DistributedSystemMXBean
@@ -50,7 +50,7 @@ This MBean also provides some MBean model navigation APIS. These APIs should be
| Object Name | GemFire:type=Distributed,service=System |
| Instances Per Node | 1 |
-See the `com.gemstone.gemfire.management.DistributedSystemMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.DistributedSystemMXBean` JavaDocs for information on available MBean methods and attributes.
## <a id="topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_48384B091AB846E591F22EEA2770DD36" class="no-quick-link"></a>DistributedRegionMXBean
@@ -65,7 +65,7 @@ System-wide aggregate MBean of a named region. It provides a high-level view of
| Object Name | GemFire:type=Distributed,service=Region,name=<regionName> |
| Instances Per Node | 0..N |
-See the `com.gemstone.gemfire.management.DistributedRegionMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.DistributedRegionMXBean` JavaDocs for information on available MBean methods and attributes.
## <a id="topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_9E004D8AA3D24647A5C19CAA1879F0A4" class="no-quick-link"></a>DistributedLockServiceMXBean
@@ -82,7 +82,7 @@ A named instance of DistributedLockService defines a space for locking arbitrary
| Object Name | GemFire:type=Distributed,service=LockService,name=<dlsName> |
| Instances Per Node | 0..N |
-See the `com.gemstone.gemfire.management.DistributedLockServiceMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.DistributedLockServiceMXBean` JavaDocs for information on available MBean methods and attributes.
## <a id="topic_48194A5BDF3F40F68E95A114DD702413" class="no-quick-link"></a>Managed Node MBeans
@@ -115,7 +115,7 @@ See [MemberMXBean Notifications](list_of_mbean_notifications.html#reference_czt_
| Object Name | GemFire:type=Member,member=<name-or-dist-member-id> |
| Instances Per Node | 1 |
-See the `com.gemstone.gemfire.management.MemberMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.MemberMXBean` JavaDocs for information on available MBean methods and attributes.
## <a id="topic_48194A5BDF3F40F68E95A114DD702413__section_7287A7560650426E9B8249E2D87CE55F" class="no-quick-link"></a>CacheServerMXBean
@@ -132,7 +132,7 @@ See [CacheServerMXBean Notifications](list_of_mbean_notifications.html#cacheserv
| Object Name | GemFire:type=Member,service=CacheServer,member=<name-or-dist-member-id> |
| Instances Per Node | 1 |
-See the `com.gemstone.gemfire.management.CacheServerMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.CacheServerMXBean` JavaDocs for information on available MBean methods and attributes.
## <a id="topic_48194A5BDF3F40F68E95A114DD702413__section_577A666924E54352AF69294DC8DEFEBF" class="no-quick-link"></a>RegionMXBean
@@ -147,7 +147,7 @@ Member's local view of region.
| Object Name | GemFire:type=Member,service=Region,name=<regionName>,member=<name-or-dist-member-id> |
| Instances Per Node | 0..N |
-See the `com.gemstone.gemfire.management.RegionMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.RegionMXBean` JavaDocs for information on available MBean methods and attributes.
## <a id="topic_48194A5BDF3F40F68E95A114DD702413__section_2F9F00081BB14CE0ADA251F5B6289BF2" class="no-quick-link"></a>LockServiceMXBean
@@ -162,7 +162,7 @@ Represents a named instance of a LockService . Any number of LockServices can be
| Object Name | GemFire:type=Member,service=LockService,name=<dlsName>,member=<name-or-dist-member-id> |
| Instances Per Node | 0..N |
-See the `com.gemstone.gemfire.management.LockServiceMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.LockServiceMXBean` JavaDocs for information on available MBean methods and attributes.
## <a id="topic_48194A5BDF3F40F68E95A114DD702413__section_1F475F68E73B4EAE875BA40825E736C9" class="no-quick-link"></a>DiskStoreMXBean
@@ -177,7 +177,7 @@ Represents a DiskStore object which provides disk storage for one or more region
| Object Name | GemFire:type=Member,service=DiskStore,name=<name>,member=<name-or-dist-member-id> |
| Instances Per Node | 0..N |
-See the `com.gemstone.gemfire.management.DiskStoreMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.DiskStoreMXBean` JavaDocs for information on available MBean methods and attributes.
## <a id="topic_48194A5BDF3F40F68E95A114DD702413__section_6A77030A15704BFEAEBBD7DB88266BF6" class="no-quick-link"></a>AsyncEventQueueMXBean
@@ -192,7 +192,7 @@ An AsyncEventQueueMXBean provides access to an AsyncEventQueue, which represent
| Object Name | GemFire:type=Member,service=AsyncEventQueue=<AsyncEventQueue> ,member=<name-or-dist-member-id> |
| Instances Per Node | 0..N |
-See the `com.gemstone.gemfire.management.AsyncEventQueueMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.AsyncEventQueueMXBean` JavaDocs for information on available MBean methods and attributes.
## <a id="topic_48194A5BDF3F40F68E95A114DD702413__section_BB83107990D346F39271ACCC14CB84A0" class="no-quick-link"></a>LocatorMXBean
@@ -207,4 +207,4 @@ A LocatorMXBean represents a locator .
| Object Name | GemFire:type=Member,service=Locator,port=<port>,member=<name-or-dist-member-id> |
| Instances Per Node | 0..1 |
-See the `com.gemstone.gemfire.management.LocatorMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.LocatorMXBean` JavaDocs for information on available MBean methods and attributes.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/management/management_system_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/management/management_system_overview.html.md.erb b/managing/management/management_system_overview.html.md.erb
index 08a5979..33809b0 100644
--- a/managing/management/management_system_overview.html.md.erb
+++ b/managing/management/management_system_overview.html.md.erb
@@ -79,9 +79,9 @@ You can use the Geode management APIs to accomplish the following tasks:
- View persistent member information such as disk store ID.
- Browse region attributes.
-See the JavaDocs for the `com.gemstone.gemfire.management` package for more details.
+See the JavaDocs for the `org.apache.geode.management` package for more details.
-You can also execute gfsh commands using the ManagementService API. See [Executing gfsh Commands through the Management API](gfsh_and_management_api.html#concept_451F0978285245E69C3E8DE795BD8635) and the JavaDocs for the `com.gemstone.gemfire.management.cli` package.
+You can also execute gfsh commands using the ManagementService API. See [Executing gfsh Commands through the Management API](gfsh_and_management_api.html#concept_451F0978285245E69C3E8DE795BD8635) and the JavaDocs for the `org.apache.geode.management.cli` package.
## <a id="concept_1BAE2CE1146B4347ABD61F50B9F9781F__section_E69A93A6309E4747B52850D81FE1674E" class="no-quick-link"></a>Geode Management and Monitoring Tools
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/management/mm_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/management/mm_overview.html.md.erb b/managing/management/mm_overview.html.md.erb
index 43f280f..b21c7d1 100644
--- a/managing/management/mm_overview.html.md.erb
+++ b/managing/management/mm_overview.html.md.erb
@@ -60,7 +60,7 @@ See [Apache Geode Management and Monitoring](management_and_monitoring.html)
## Geode Java API
-The Geode API provides a set of Java classes you can use to manage and monitor a distributed system. See the <span class="keyword apiname">com.gemstone.gemfire.management</span> package in the Geode JavaDocs .
+The Geode API provides a set of Java classes you can use to manage and monitor a distributed system. See the <span class="keyword apiname">org.apache.geode.management</span> package in the Geode JavaDocs .
## Geode Pulse
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/management/programming_example.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/management/programming_example.html.md.erb b/managing/management/programming_example.html.md.erb
index 6380788..45e4ac5 100644
--- a/managing/management/programming_example.html.md.erb
+++ b/managing/management/programming_example.html.md.erb
@@ -11,11 +11,11 @@ package quickstart;
import java.util.Set;
import javax.management.ObjectName;
-import com.gemstone.gemfire.cache.Cache;
-import com.gemstone.gemfire.cache.CacheFactory;
-import com.gemstone.gemfire.distributed.DistributedMember;
-import com.gemstone.gemfire.management.ManagementService;
-import com.gemstone.gemfire.management.RegionMXBean;
+import org.apache.geode.cache.Cache;
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.distributed.DistributedMember;
+import org.apache.geode.management.ManagementService;
+import org.apache.geode.management.RegionMXBean;
/**
* Example of a JMX Manager Node. It first creates a cache.
@@ -116,11 +116,11 @@ package quickstart;
import java.io.BufferedReader;
import java.io.InputStreamReader;
-import com.gemstone.gemfire.cache.Cache;
-import com.gemstone.gemfire.cache.CacheFactory;
-import com.gemstone.gemfire.cache.Region;
-import com.gemstone.gemfire.management.ManagementService;
-import com.gemstone.gemfire.management.RegionMXBean;
+import org.apache.geode.cache.Cache;
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.cache.Region;
+import org.apache.geode.management.ManagementService;
+import org.apache.geode.management.RegionMXBean;
/**
* In this example of Managed Node.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/monitor_tune/performance_controls.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/monitor_tune/performance_controls.html.md.erb b/managing/monitor_tune/performance_controls.html.md.erb
index dcc91b7..79269a0 100644
--- a/managing/monitor_tune/performance_controls.html.md.erb
+++ b/managing/monitor_tune/performance_controls.html.md.erb
@@ -12,7 +12,7 @@ Before you begin, you should understand Apache Geode [Basic Configuration and Pr
- **[Setting Cache Timeouts](../../managing/monitor_tune/performance_controls_setting_cache_timeouts.html)**
- Cache timeout properties can modified through the gfsh `alter runtime` command (or declared in the `cache.xml` file) and can also be set through methods of the interface, `com.gemstone.gemfire.cache.Cache`.
+ Cache timeout properties can modified through the gfsh `alter runtime` command (or declared in the `cache.xml` file) and can also be set through methods of the interface, `org.apache.geode.cache.Cache`.
- **[Controlling Socket Use](../../managing/monitor_tune/performance_controls_controlling_socket_use.html)**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/monitor_tune/performance_controls_controlling_socket_use.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/monitor_tune/performance_controls_controlling_socket_use.html.md.erb b/managing/monitor_tune/performance_controls_controlling_socket_use.html.md.erb
index ca98ace..4e04445 100644
--- a/managing/monitor_tune/performance_controls_controlling_socket_use.html.md.erb
+++ b/managing/monitor_tune/performance_controls_controlling_socket_use.html.md.erb
@@ -13,7 +13,7 @@ When conserve-sockets is set to false, each application thread uses a dedicated
**Note:**
When you have transactions operating on EMPTY, NORMAL or PARTITION regions, make sure that `conserve-sockets` is set to false to avoid distributed deadlocks.
-You can override the `conserve-sockets` setting for individual threads. These methods are in `com.gemstone.gemfire.distributed.DistributedSystem`:
+You can override the `conserve-sockets` setting for individual threads. These methods are in `org.apache.geode.distributed.DistributedSystem`:
- `setThreadsSocketPolicy`. Sets the calling thread\u2019s individual socket policy, overriding the policy set for the application as a whole. If set to true, the calling thread shares socket connections with other threads. If false, the calling thread has its own sockets.
- `releaseThreadsSockets`. Frees any sockets held by the calling thread. Threads hold their own sockets only when conserve-sockets is false. Threads holding their own sockets can call this method to avoid holding the sockets until the socket-lease-time has expired.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/monitor_tune/performance_controls_setting_cache_timeouts.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/monitor_tune/performance_controls_setting_cache_timeouts.html.md.erb b/managing/monitor_tune/performance_controls_setting_cache_timeouts.html.md.erb
index f322017..bb84a5f 100644
--- a/managing/monitor_tune/performance_controls_setting_cache_timeouts.html.md.erb
+++ b/managing/monitor_tune/performance_controls_setting_cache_timeouts.html.md.erb
@@ -2,7 +2,7 @@
title: Setting Cache Timeouts
---
-Cache timeout properties can modified through the gfsh `alter runtime` command (or declared in the `cache.xml` file) and can also be set through methods of the interface, `com.gemstone.gemfire.cache.Cache`.
+Cache timeout properties can modified through the gfsh `alter runtime` command (or declared in the `cache.xml` file) and can also be set through methods of the interface, `org.apache.geode.cache.Cache`.
To modify cache timeout properties, you can issue the following `gfsh alter runtime` command. For example:
@@ -12,7 +12,7 @@ gfsh>alter runtime --search-timeout=150
The `--search-timeout` parameter specifies how long a netSearch operation can wait for data before timing out. The default is 5 minutes. You may want to change this based on your knowledge of the network load or other factors.
-The next two configurations describe timeout settings for locking in regions with global scope. Locking operations can time out in two places: when waiting to obtain a lock (lock time out); and when holding a lock (lock lease time). Operations that modify objects in a global region use automatic locking. In addition, you can manually lock a global region and its entries through `com.gemstone.gemfire.cache.Region`. The explicit lock methods provided by the APIs allow you to specify a lock timeout parameter. The lock time out for implicit operations and the lock lease time for implicit and explicit operations are governed by these cache-wide settings:
+The next two configurations describe timeout settings for locking in regions with global scope. Locking operations can time out in two places: when waiting to obtain a lock (lock time out); and when holding a lock (lock lease time). Operations that modify objects in a global region use automatic locking. In addition, you can manually lock a global region and its entries through `org.apache.geode.cache.Region`. The explicit lock methods provided by the APIs allow you to specify a lock timeout parameter. The lock time out for implicit operations and the lock lease time for implicit and explicit operations are governed by these cache-wide settings:
``` pre
gfsh>alter runtime --lock-timeout=30 --lock-lease=60
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/monitor_tune/sockets_and_gateways.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/monitor_tune/sockets_and_gateways.html.md.erb b/managing/monitor_tune/sockets_and_gateways.html.md.erb
index 180ea1c..4910453 100644
--- a/managing/monitor_tune/sockets_and_gateways.html.md.erb
+++ b/managing/monitor_tune/sockets_and_gateways.html.md.erb
@@ -102,4 +102,4 @@ A client, server, gateway sender, or gateway receiver produces a SocketTimeoutEx
Response:
-Increase the default socket timeout setting for the member. This timeout is set separately for the client Pool and for the gateway sender and gateway receiver, either in the `cache.xml` file or through the API. For a client/server configuration, adjust the "read-timeout" value as described in [<pool>](../../reference/topics/client-cache.html#cc-pool) or use the `com.gemstone.gemfire.cache.client.PoolFactory.setReadTimeout` method. For a gateway sender or gateway receiver, see [WAN Configuration](../../reference/topics/elements_ref.html#topic_7B1CABCAD056499AA57AF3CFDBF8ABE3).
+Increase the default socket timeout setting for the member. This timeout is set separately for the client Pool and for the gateway sender and gateway receiver, either in the `cache.xml` file or through the API. For a client/server configuration, adjust the "read-timeout" value as described in [<pool>](../../reference/topics/client-cache.html#cc-pool) or use the `org.apache.geode.cache.client.PoolFactory.setReadTimeout` method. For a gateway sender or gateway receiver, see [WAN Configuration](../../reference/topics/elements_ref.html#topic_7B1CABCAD056499AA57AF3CFDBF8ABE3).
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/region_compression/region_compression.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/region_compression/region_compression.html.md.erb b/managing/region_compression/region_compression.html.md.erb
index c6b3298..d664a7b 100644
--- a/managing/region_compression/region_compression.html.md.erb
+++ b/managing/region_compression/region_compression.html.md.erb
@@ -73,7 +73,7 @@ To enable compression on your region, set the following region attribute in your
<region name="compressedRegion" >
<region-attributes data-policy="replicate" ... />
<Compressor>
- <class-name>com.gemstone.gemfire.compression.SnappyCompressor</class-name>
+ <class-name>org.apache.geode.compression.SnappyCompressor</class-name>
</Compressor>
...
</region-attributes>
@@ -88,7 +88,7 @@ Compression can be enabled during region creation using gfsh or programmatically
Using gfsh:
``` pre
-gfsh>create-region --name=\u201dCompressedRegion\u201d --compressor=\u201dcom.gemstone.gemfire.compression.SnappyCompressor\u201d;
+gfsh>create-region --name=\u201dCompressedRegion\u201d --compressor=\u201dorg.apache.geode.compression.SnappyCompressor\u201d;
```
API:
@@ -126,7 +126,7 @@ This example provides a custom Compressor implementation:
``` pre
package com.mybiz.myproduct.compression;
-import com.gemstone.gemfire.compression.Compressor;
+import org.apache.geode.compression.Compressor;
public class LZWCompressor implements Compressor {
private final LZWCodec lzwCodec = new LZWCodec();
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/security/authentication_examples.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/authentication_examples.html.md.erb b/managing/security/authentication_examples.html.md.erb
index 9c75e61..a923679 100644
--- a/managing/security/authentication_examples.html.md.erb
+++ b/managing/security/authentication_examples.html.md.erb
@@ -17,7 +17,7 @@ These are the `gemfire.properties` file (or `gfsecurity.properties` file if you
- Client:
``` pre
- security-client-auth-init=com.gemstone.gemfire.security.templates.UserPasswordAuthInit.create
+ security-client-auth-init=org.apache.geode.security.templates.UserPasswordAuthInit.create
security-username="username"
security-password="password"
```
@@ -25,8 +25,8 @@ These are the `gemfire.properties` file (or `gfsecurity.properties` file if you
- Server system members:
``` pre
- security-peer-auth-init=com.gemstone.gemfire.security.templates.UserPasswordAuthInit.create
- security-peer-authenticator=com.gemstone.gemfire.security.templates.LdapUserAuthenticator.create
+ security-peer-auth-init=org.apache.geode.security.templates.UserPasswordAuthInit.create
+ security-peer-authenticator=org.apache.geode.security.templates.LdapUserAuthenticator.create
security-ldap-server="name of ldap server"
security-ldap-basedn="ou=www, dc=xxx, dc=yyy, dc=zzz"
```
@@ -48,7 +48,7 @@ These are the `gemfire.properties` file (or `gfsecurity.properties` file if you
- Client:
``` pre
- security-client-auth-init=com.gemstone.gemfire.security.templates.PKCSAuthInit.create
+ security-client-auth-init=org.apache.geode.security.templates.PKCSAuthInit.create
security-keystorepath="keystore path"
security-alias="alias"
security-keystorepass="keystore password"
@@ -57,7 +57,7 @@ These are the `gemfire.properties` file (or `gfsecurity.properties` file if you
- Server:
``` pre
- security-client-authenticator=com.gemstone.gemfire.security.templates.PKCSAuthenticator.create
+ security-client-authenticator=org.apache.geode.security.templates.PKCSAuthenticator.create
security-publickey-filepath="path and name of public key file"
security-publickey-pass="password of public key file store on the server"
```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/security/how_authorization_works.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/how_authorization_works.html.md.erb b/managing/security/how_authorization_works.html.md.erb
index 4a2a9b3..2dfe16e 100644
--- a/managing/security/how_authorization_works.html.md.erb
+++ b/managing/security/how_authorization_works.html.md.erb
@@ -9,7 +9,7 @@ Access rights can be checked before the client operation is performed and before
<img src="../../images/security-4.gif" id="how_authorization_works__image_254428E85E8B47F9B558DA4C5DC02B93" class="image" />
The principal, which you associate with the client when it is authenticated, is used by the authorization plug-in to allow or disallow each operation. Geode security invokes this callback with the principal and the requested operation, and permits or bars the operation depending on the result of the callback. The callback also has access to the operation data, such as the key and value for a `put`, which you can use to determine authorization. In addition, you can program the callback to change some of the operation data, such as the value for a `put` or the operation result.
-All client operations sent to the server can be authorized. The operations checked by the server are listed in `com.gemstone.gemfire.cache.operations.OperationContext.OperationCode`.
+All client operations sent to the server can be authorized. The operations checked by the server are listed in `org.apache.geode.cache.operations.OperationContext.OperationCode`.
**Note:**
`Region` query shortcut methods are all sent to the server as `query` operations.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/security/implementing_authentication.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_authentication.html.md.erb b/managing/security/implementing_authentication.html.md.erb
index d62ae6f..0ca7bc6 100644
--- a/managing/security/implementing_authentication.html.md.erb
+++ b/managing/security/implementing_authentication.html.md.erb
@@ -14,7 +14,7 @@ Use the following procedure to implement authentication in your Geode applicatio
- Obtain the properties dynamically in the `AuthInitialize.getCredentials` method.
3. For joining members, program and configure the credentials initialization plug-in:
- 1. Create an implementation of the Geode `com.gemstone.gemfire.security.AuthInitialize` interface.
+ 1. Create an implementation of the Geode `org.apache.geode.security.AuthInitialize` interface.
1. Program a public static method to return an instance of the class.
2. Program the `getCredentials` method to create all properties required by the `Authorize` method via the member's credentials.
@@ -37,7 +37,7 @@ Use the following procedure to implement authentication in your Geode applicatio
4. For all members, set any additional `gemfire.properties` (or `gfsecurity.properties` file if you are creating a special restricted access file for security configuration) `security-*` properties required by your `AuthInitialize` implementation.
4. For authorizing members, program and configure the credentials authorization plug-in:
- 1. Implement the Geode `com.gemstone.gemfire.security.Authenticator` interface:
+ 1. Implement the Geode `org.apache.geode.security.Authenticator` interface:
1. Program a public static, zero-argument method to return an instance of the class.
2. Program the `authenticate` method to authenticate the credentials and return a `java.security.Principal` object.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/security/implementing_authorization.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_authorization.html.md.erb b/managing/security/implementing_authorization.html.md.erb
index 988ae87..5c68d02 100644
--- a/managing/security/implementing_authorization.html.md.erb
+++ b/managing/security/implementing_authorization.html.md.erb
@@ -8,7 +8,7 @@ To set up authorized access control for the cache:
1. Determine the degree of control you want over client access to the server cache
2. Program and configure the authorization plug-in:
- 1. Create an implementation of the Geode `com.gemstone.gemfire.security.AccessControl` interface
+ 1. Create an implementation of the Geode `org.apache.geode.security.AccessControl` interface
1. Program a public static method to return an instance of the class.
2. Program the `init` method to store all properties required by the `AccessControl.authorizeOperation` method at the time the client makes its connection to the server.
**Note:**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/statistics/application_defined_statistics.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/statistics/application_defined_statistics.html.md.erb b/managing/statistics/application_defined_statistics.html.md.erb
index 7c7e29f..8a4743b 100644
--- a/managing/statistics/application_defined_statistics.html.md.erb
+++ b/managing/statistics/application_defined_statistics.html.md.erb
@@ -5,7 +5,7 @@ title: Application-Defined and Custom Statistics
Geode includes interfaces for defining and maintaining your own statistics.
<a id="application_defined_statistics__section_88C31FA62A194947BF71AD54B5F9BAB3"></a>
-The Geode package, `com.gemstone.gemfire`, includes the following interfaces for defining and maintaining your own statistics:
+The Geode package, `org.apache.geode`, includes the following interfaces for defining and maintaining your own statistics:
- **StatisticDescriptor**. Describes an individual statistic. Each statistic has a name and information on the statistic it holds, such as its class type (long, int, etc.) and whether it is a counter that always increments, or a gauge that can vary in any manner.
- **StatisticsType**. Logical type that holds a list of `StatisticDescriptors` and provides access methods to them. The `StatisticDescriptors` contained by a `StatisticsType` are each assigned a unique ID within the list. `StatisticsType` is used to create a `Statistics` instance.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/troubleshooting/diagnosing_system_probs.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/troubleshooting/diagnosing_system_probs.html.md.erb b/managing/troubleshooting/diagnosing_system_probs.html.md.erb
index e5577bf..1e71ace 100644
--- a/managing/troubleshooting/diagnosing_system_probs.html.md.erb
+++ b/managing/troubleshooting/diagnosing_system_probs.html.md.erb
@@ -42,17 +42,17 @@ Exception in thread "main" java.lang.RuntimeException: An IO error occurred whil
starting a Locator in C:\devel\gfcache\locator\locator on 192.0.2.0[10999]: Network is
unreachable; port (10999) is not available on 192.0.2.0.
at
-com.gemstone.gemfire.distributed.LocatorLauncher.start(LocatorLauncher.java:622)
+org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:622)
at
-com.gemstone.gemfire.distributed.LocatorLauncher.run(LocatorLauncher.java:513)
+org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:513)
at
-com.gemstone.gemfire.distributed.LocatorLauncher.main(LocatorLauncher.java:188)
+org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:188)
Caused by: java.net.BindException: Network is unreachable; port (10999) is not available on
192.0.2.0.
at
-com.gemstone.gemfire.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:136)
+org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:136)
at
-com.gemstone.gemfire.distributed.LocatorLauncher.start(LocatorLauncher.java:596)
+org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:596)
...
```
@@ -115,14 +115,14 @@ Response:
System member startup fails with an error like one of these:
``` pre
-Exception in thread "main" com.gemstone.gemfire.cache.CacheXmlException:
+Exception in thread "main" org.apache.geode.cache.CacheXmlException:
While reading Cache XML file:/C:/gemfire/client_cache.xml.
Error while parsing XML, caused by org.xml.sax.SAXParseException:
Document root element "client-cache", must match DOCTYPE root "cache".
```
``` pre
-Exception in thread "main" com.gemstone.gemfire.cache.CacheXmlException:
+Exception in thread "main" org.apache.geode.cache.CacheXmlException:
While reading Cache XML file:/C:/gemfire/cache.xml.
Error while parsing XML, caused by org.xml.sax.SAXParseException:
Document root element "cache", must match DOCTYPE root "client-cache".
@@ -199,7 +199,7 @@ Response: Use a partitioned or replicate data-policy for your server regions. Th
In partitioned regions that are persisted to disk, if you have any members offline, the partitioned region will still be available but may have some buckets represented only in offline disk stores. In this case, methods that access the bucket entries return a PartitionOfflineException, similar to this:
``` pre
-com.gemstone.gemfire.cache.persistence.PartitionOfflineException:
+org.apache.geode.cache.persistence.PartitionOfflineException:
Region /__PR/_B__root_partitioned__region_7 has persistent data that is no
longer online stored at these locations:
[/192.0.2.1:/export/straw3/users/jpearson/bugfix_Apr10/testCL/hostB/backupDirectory
@@ -247,7 +247,7 @@ The process may be hitting its virtual address space limits. The virtual address
## <a id="diagnosing_system_probs__section_B49BD03F4CA241C7BED4A2C4D5936A7A" class="no-quick-link"></a>PartitionedRegionDistributionException
-The com.gemstone.gemfire.cache.PartitionedRegionDistributionException appears when Geode fails after many attempts to complete a distributed operation. This exception indicates that no data store member can be found to perform a destroy, invalidate, or get operation.
+The org.apache.geode.cache.PartitionedRegionDistributionException appears when Geode fails after many attempts to complete a distributed operation. This exception indicates that no data store member can be found to perform a destroy, invalidate, or get operation.
Response:
@@ -257,7 +257,7 @@ Response:
## <a id="diagnosing_system_probs__section_7DE15A6C99974821B6CA418BC2AF98F1" class="no-quick-link"></a>PartitionedRegionStorageException
-The com.gemstone.gemfire.cache.PartitionedRegionStorageException appears when Geode can\u2019t create a new entry. This exception arises from a lack of storage space for put and create operations or for get operations with a loader. PartitionedRegionStorageException often indicates data loss or impending data loss.
+The org.apache.geode.cache.PartitionedRegionStorageException appears when Geode can\u2019t create a new entry. This exception arises from a lack of storage space for put and create operations or for get operations with a loader. PartitionedRegionStorageException often indicates data loss or impending data loss.
The text string indicates the cause of the exception, as in these examples:
@@ -299,7 +299,7 @@ A client and server produces a SocketTimeoutException when it stops waiting for
Response:
-Increase the default socket timeout setting for the member. This timeout is set separately for the client Pool. For a client/server configuration, adjust the "read-timeout" value as described in [<pool>](../../reference/topics/client-cache.html#cc-pool) or use the `com.gemstone.gemfire.cache.client.PoolFactory.setReadTimeout` method.
+Increase the default socket timeout setting for the member. This timeout is set separately for the client Pool. For a client/server configuration, adjust the "read-timeout" value as described in [<pool>](../../reference/topics/client-cache.html#cc-pool) or use the `org.apache.geode.cache.client.PoolFactory.setReadTimeout` method.
## <a id="diagnosing_system_probs__section_8C7CB2EA0A274DAF90083FECE0BF3B1F" class="no-quick-link"></a>Member logs ForcedDisconnectException, Cache and DistributedSystem forcibly closed
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/troubleshooting/recovering_from_p2p_crashes.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/troubleshooting/recovering_from_p2p_crashes.html.md.erb b/managing/troubleshooting/recovering_from_p2p_crashes.html.md.erb
index 8876219..47e55df 100644
--- a/managing/troubleshooting/recovering_from_p2p_crashes.html.md.erb
+++ b/managing/troubleshooting/recovering_from_p2p_crashes.html.md.erb
@@ -113,7 +113,7 @@ successfully allocated = 0 number needed = 2 Data stores available:
Exception:
``` pre
-com.gemstone.gemfire.cache.PartitionedRegionStorageException: Unable to find any members to
+org.apache.geode.cache.PartitionedRegionStorageException: Unable to find any members to
host a bucket in the partitioned region.
```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/managing/troubleshooting/system_failure_and_recovery.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/troubleshooting/system_failure_and_recovery.html.md.erb b/managing/troubleshooting/system_failure_and_recovery.html.md.erb
index df213c6..603fd5f 100644
--- a/managing/troubleshooting/system_failure_and_recovery.html.md.erb
+++ b/managing/troubleshooting/system_failure_and_recovery.html.md.erb
@@ -157,7 +157,7 @@ It is likely that all processes using the locators will exit with the same messa
Alert:
``` pre
-Membership service failure: Channel closed: com.gemstone.gemfire.ForcedDisconnectException:
+Membership service failure: Channel closed: org.apache.geode.ForcedDisconnectException:
There are no processes eligible to be group membership coordinator
(last coordinator left view)
```
@@ -173,7 +173,7 @@ The operator should examine the locator processes and logs, and restart the loca
Alert:
``` pre
-Membership service failure: Channel closed: com.gemstone.gemfire.ForcedDisconnectException:
+Membership service failure: Channel closed: org.apache.geode.ForcedDisconnectException:
There are no processes eligible to be group membership coordinator
(all eligible coordinators are suspect)
```
@@ -189,7 +189,7 @@ The operator should examine the locator processes and logs, and restart the loca
Alert:
``` pre
-Membership service failure: Channel closed: com.gemstone.gemfire.ForcedDisconnectException:
+Membership service failure: Channel closed: org.apache.geode.ForcedDisconnectException:
Unable to contact any locators and network partition detection is enabled
```
@@ -204,7 +204,7 @@ The operator should examine the locator processes and logs, and restart the loca
Alert:
``` pre
-Membership service failure: Channel closed: com.gemstone.gemfire.ForcedDisconnectException:
+Membership service failure: Channel closed: org.apache.geode.ForcedDisconnectException:
Disconnected as a slow-receiver
```
@@ -252,7 +252,7 @@ The operator can turn this off by setting the system property gemfire.disable-sa
Alert:
``` pre
-Membership service failure: Channel closed: com.gemstone.gemfire.ForcedDisconnectException:
+Membership service failure: Channel closed: org.apache.geode.ForcedDisconnectException:
This member has been forced out of the Distributed System. Please consult GemFire logs to
find the reason.
```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/reference/topics/cache_xml.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/cache_xml.html.md.erb b/reference/topics/cache_xml.html.md.erb
index add0e29..a1969d4 100644
--- a/reference/topics/cache_xml.html.md.erb
+++ b/reference/topics/cache_xml.html.md.erb
@@ -8,7 +8,7 @@ This section documents the `cache.xml` sub-elements used for Geode server config
For Geode client configuration, see [<client-cache> Element Reference](client-cache.html#cc-client-cache).
-**API**:`com.gemstone.gemfire.cache.CacheFactory`
+**API**:`org.apache.geode.cache.CacheFactory`
<a id="cache_xml_cache__table_B079C5A320194B3A98AD82DDB67DA43D"></a>
@@ -126,7 +126,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
## <a id="dynamic-region-factory" class="no-quick-link"></a><dynamic-region-factory>
-The `<dynamic-region-factory>` element configures a dynamic region factory for this cache. You can use this element to dynamically create regions in your application code. Use the <span class="keyword apiname">createDynamicRegion()</span> method of the <span class="keyword apiname">com.gemstone.gemfire.cache.DynamicRegionFactory</span> class in your Java code to dynamically create regions.
+The `<dynamic-region-factory>` element configures a dynamic region factory for this cache. You can use this element to dynamically create regions in your application code. Use the <span class="keyword apiname">createDynamicRegion()</span> method of the <span class="keyword apiname">org.apache.geode.cache.DynamicRegionFactory</span> class in your Java code to dynamically create regions.
**Note:**
You can not use this element to dynamically create *partitioned* regions.
@@ -137,7 +137,7 @@ The optional `<disk-dir>` sub-element specifies the directory to store the persi
Set the `pool-name` attribute to set the name of the connection pool used by client applications in a client/server cache configuration. Do not specify the `pool-name` attribute in servers or peers.
-**API:** `com.gemstone.gemfire.cache.DynamicRegionFactory`
+**API:** `org.apache.geode.cache.DynamicRegionFactory`
<a id="dynamic-region-factory__table_6B7271DE968946CC9757FE241E9F872C"></a>
@@ -201,7 +201,7 @@ Specifies a region or disk store's disk directory.
Configures a queue for sending region events to an AsyncEventListener implementation (for example, for write-behind event handling).
-**API:** `com.gemstone.gemfire.cache.asyncqueue.AsyncEventQueue`
+**API:** `org.apache.geode.cache.asyncqueue.AsyncEventQueue`
<a id="async-event-queue__table_5CEA4FE481D741E4913C098B67735714"></a>
@@ -326,7 +326,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<gateway-event-filter>
- <class-name>com.gemstone.gemfire.util.SampleEventFilter</class-name>
+ <class-name>org.apache.geode.util.SampleEventFilter</class-name>
<parameter name="param1">
<string>"value1"</string>
</parameter>
@@ -343,7 +343,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<gateway-event-substitution-filter>
- <class-name>com.gemstone.gemfire.util.SampleEventSubstitutionFilter</class-name>
+ <class-name>org.apache.geode.util.SampleEventSubstitutionFilter</class-name>
<parameter name="param1">
<string>"value1"</string>
</parameter>
@@ -356,7 +356,7 @@ An AsyncEventListener receives callbacks for events that change region data. You
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements. See [<class-name> and <parameter>](#class-name_parameter).
-**API:** `com.gemstone.gemfire.cache.asyncqueue.AsyncEventListener`
+**API:** `org.apache.geode.cache.asyncqueue.AsyncEventListener`
**Example:**
@@ -381,9 +381,9 @@ Specify the Java class and its initialization parameters with the `<class-name>`
Configures the cache to serve region data to clients in a client/server caching system. This element indicates the port the server listens on for client communication.
-The `cacheserver` process uses only `cache.xml` configuration. For application servers, you can set the same configuration properties using the `com.gemstone.gemfire.cache.server.CacheServer` and `com.gemstone.gemfire.cache.Cache` interfaces. For detailed information, see the online Java API documentation.
+The `cacheserver` process uses only `cache.xml` configuration. For application servers, you can set the same configuration properties using the `org.apache.geode.cache.server.CacheServer` and `org.apache.geode.cache.Cache` interfaces. For detailed information, see the online Java API documentation.
-**API:** `com.gemstone.gemfire.cache.server.CacheServer`
+**API:** `org.apache.geode.cache.server.CacheServer`
<a id="cache-server__table_78A30804A5394C2AA190579C8A1E22D8"></a>
@@ -534,7 +534,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
**Default:** If this is not defined, the default Geode load probe is used.
-**API:** `com.gemstone.gemfire.cache.server.setLoadProbe`
+**API:** `org.apache.geode.cache.server.setLoadProbe`
**Example:**
@@ -550,7 +550,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
Use for client caches. Defines a client's server pool used to communicate with servers running in a different distributed system.
-**API:** `com.gemstone.gemfire.cache.client.PoolFactory`
+**API:** `org.apache.geode.cache.client.PoolFactory`
<a id="pool__table_14D991AC65A6414BB71EF7AC67B59771"></a>
@@ -714,7 +714,7 @@ Addresses and ports of the locators to connect to. You can define multiple locat
**Note:**
Provide a locator list or `server` list, but not both.
-**API:** `com.gemstone.gemfire.distributed.LocatorLauncher`
+**API:** `org.apache.geode.distributed.LocatorLauncher`
<a id="locator__table_10BEB4E1383B475795ED4E290676E058"></a>
@@ -743,7 +743,7 @@ Provide a server list or `locator` list, but not both.
**Default:**
-**API:** `com.gemstone.gemfire.distributed.ServerLauncher`
+**API:** `org.apache.geode.distributed.ServerLauncher`
<a id="server__table_BD0B19AA44FF4CA68BBBC785E46E03F1"></a>
@@ -770,7 +770,7 @@ Defines a pool of one or more disk stores, which can be used by regions, and cli
**Default:** The cache default disk store, named "DEFAULT", is used when disk is used but no disk store is named.
-**API:** `com.gemstone.gemfire.cache.DiskStore`
+**API:** `org.apache.geode.cache.DiskStore`
<a id="disk-store__table_C90DEC71FBD74C2F98E5447E961E899F"></a>
@@ -908,7 +908,7 @@ Specifies a region or disk store's disk directory.
Specifies the configuration for the Portable Data eXchange (PDX) method of serialization.
-**API:** `com.gemstone.gemfire.cache.CacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields` and `com.gemstone.gemfire.cache.ClientCacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields`
+**API:** `org.apache.geode.cache.CacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields` and `org.apache.geode.cache.ClientCacheFactory.setPdxReadSerialized`, `setPdxDiskStore`, `setPdxPersistent`, `setPdxIgnoreUnreadFields`
<a id="pdx__table_DE49C41CAD444DA9B01F055C401920BF"></a>
@@ -928,7 +928,7 @@ Specifies the configuration for the Portable Data eXchange (PDX) method of seria
<pdx persistent="true" disk-store-name="myDiskStore">
<pdx-serializer>
<class-name>
- com.gemstone.gemfire.pdx.ReflectionBasedAutoSerializer
+ org.apache.geode.pdx.ReflectionBasedAutoSerializer
</class-name>
<parameter name="classes">
<string>com.company.domain.DomainObject</string>>
@@ -947,7 +947,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
**Default:**
-**API:** `com.gemstone.gemfire.cache.CacheFactory.setPdxSerializer`
+**API:** `org.apache.geode.cache.CacheFactory.setPdxSerializer`
**Example:**
@@ -966,7 +966,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
Specifies a region attributes template that can be named (by `id`) and referenced (by `refid`) later in the `cache.xml` and through the API.
-**API:** `com.gemstone.gemfire.cache.RegionFactory` or `com.gemstone.gemfire.cache.ClientRegionFactory`
+**API:** `org.apache.geode.cache.RegionFactory` or `org.apache.geode.cache.ClientRegionFactory`
<a id="region-attributes__table_028B4DC4FB72488AB6359AAA13E0B5B0"></a>
@@ -1298,7 +1298,7 @@ Specifies a region attributes template that can be named (by `id`) and reference
</tr>
<tr class="even">
<td>statistics-enabled</td>
-<td>Boolean specifying whether to gather statistics on the region. Must be true to use expiration on the region. Geode provides a standard set of statistics for cached regions and region entries, which give you information for fine-tuning your distributed system. Unlike other Geode statistics, statistics for local and distributed regions are not archived and cannot be charted. They are kept in instances of <code class="ph codeph">com.gemstone.gemfire.cache.CacheStatistics</code> and made available through the region and its entries through the <code class="ph codeph">Region.getStatistics</code> and <code class="ph codeph">Region.Entry.getStatistics</code> methods.
+<td>Boolean specifying whether to gather statistics on the region. Must be true to use expiration on the region. Geode provides a standard set of statistics for cached regions and region entries, which give you information for fine-tuning your distributed system. Unlike other Geode statistics, statistics for local and distributed regions are not archived and cannot be charted. They are kept in instances of <code class="ph codeph">org.apache.geode.cache.CacheStatistics</code> and made available through the region and its entries through the <code class="ph codeph">Region.getStatistics</code> and <code class="ph codeph">Region.Entry.getStatistics</code> methods.
<p><strong>API:</strong> <code class="ph codeph">setStatisticsEnabled</code></p>
<p><strong>Example:</strong></p>
<pre class="pre codeblock language-xml"><code><region-attributes
@@ -1354,7 +1354,7 @@ Set the constraint in every cache where you create or update the region entries.
**Default:** not set
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setKeyConstraint`
+**API:** `org.apache.geode.cache.RegionFactory.setKeyConstraint`
**Example:**
@@ -1375,7 +1375,7 @@ Set the constraint in every cache where you create or update the region entries.
**Default:** not set
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setValueConstraint`
+**API:** `org.apache.geode.cache.RegionFactory.setValueConstraint`
**Example:**
@@ -1393,7 +1393,7 @@ Expiration setting that specifies how long the region can remain in the cache wi
**Default:** not set - no expiration of this type
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setRegionTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setRegionTimeToLive`
**Example:**
@@ -1484,11 +1484,11 @@ Select one of the following expiration actions:
## <a id="custom-expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -1516,7 +1516,7 @@ To ensure reliable read behavior across the partitioned region, use `region-time
**Default:** not set - no expiration of this type
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setRegionIdleTimeout`
+**API:** `org.apache.geode.cache.RegionFactory.setRegionIdleTimeout`
**Example:**
@@ -1606,11 +1606,11 @@ Select one of the following expiration actions:
## <a id="region-idle-time_custom-expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -1635,7 +1635,7 @@ Expiration setting that specifies how long the region\u2019s entries can remain in
**Default:** not set - no expiration of this type.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setEntryTimeToLive`
**Example:**
@@ -1726,11 +1726,11 @@ Select one of the following expiration actions:
## <a id="entry-time-to-live_custom_expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -1756,7 +1756,7 @@ Expiration setting that specifies how long the region\u2019s entries can remain in
**Note:**
To ensure reliable read behavior across the partitioned region, use `entry-time-to-live` for entry expiration instead of this setting.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setEntryIdleTimeout`
+**API:** `org.apache.geode.cache.RegionFactory.setEntryIdleTimeout`
**Example:**
@@ -1848,11 +1848,11 @@ Select one of the following expiration actions:
## <a id="entry-idle-time_custom-expiry" class="no-quick-link"></a><custom-expiry>
-Specifies the custom class that implements `com.gemstone.gemfire.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
+Specifies the custom class that implements `org.apache.geode.cache.CustomExpiry`. You define this class in order to override the region-wide settings for specific entries. See [Configure Data Expiration](../../developing/expiration/configuring_data_expiration.html) for an example.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
+**API:** `org.apache.geode.cache.RegionFactory.setCustomEntryIdleTimeout`, `setCustomeEntryTimeToLive`
**Example:**
@@ -1878,7 +1878,7 @@ Defines the region as partitioned and controls partitioning behavior. This is se
**Note:**
With the exception of `local-max-memory`, all members defining a partitioned region must use the same partition attribute settings.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setPartitionAttributes`
+**API:** `org.apache.geode.cache.RegionFactory.setPartitionAttributes`
<a id="partition-attributes__table_5CB4AC52DDA94E60A2B8325BA31E1253"></a>
@@ -1908,7 +1908,7 @@ With the exception of `local-max-memory`, all members defining a partitioned reg
Describes a custom PartitionResolver for a region.
-**API:** `com.gemstone.gemfire.cache.PartitionAttributesFactory.setPartitionResolver`
+**API:** `org.apache.geode.cache.PartitionAttributesFactory.setPartitionResolver`
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements. See [<class-name> and <parameter>](#class-name_parameter).
@@ -1941,7 +1941,7 @@ Defines a custom PartitionListener for a partitioned region.
Specify the Java class and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements. See [<class-name> and <parameter>](#class-name_parameter).
-**API:** `com.gemstone.gemfire.cache.PartitionAttributesFactory.PartitionListener`
+**API:** `org.apache.geode.cache.PartitionAttributesFactory.PartitionListener`
**Example:**
@@ -1960,7 +1960,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
Describes a partition in a Fixed Partitioned Region.
-**API:** `com.gemstone.gemfire.cache.PartitionAttributesFactory.addFixedPartitionAttributes`
+**API:** `org.apache.geode.cache.PartitionAttributesFactory.addFixedPartitionAttributes`
<a id="fixed-partition-attributes__table_E3929FDFD5A24946919936F67D6DE46E"></a>
@@ -1998,7 +1998,7 @@ Describes a partition in a Fixed Partitioned Region.
Establishes reliability requirements and behavior for a region. Use this to configure the region to require one or more membership roles to be running in the system for reliable access to the region. You can set up your own roles, such as producer or backup, specifying each role as a string. Membership attributes have no effect unless one or more required roles are specified.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setMembershipAttributes`
+**API:** `org.apache.geode.cache.RegionFactory.setMembershipAttributes`
<a id="membership-attributes__table_EBF62709899C48CFA1D2032656F95D0F"></a>
@@ -2088,7 +2088,7 @@ Specifies how the region is affected by resumption of reliability when one or mo
Specifies a role that is required for reliable access to the region.
-**API:** `com.gemstone.gemfire.cache.MembershipAttributes`
+**API:** `org.apache.geode.cache.MembershipAttributes`
<a id="required-role__table_8DE73CB4967F4906ACEF6FFFB91186B7"></a>
@@ -2115,7 +2115,7 @@ Specifies subscriber requirements and behavior for the region. There is one subs
**Note:**
The interest policy determines which events are delivered, but the `data-policy` determines how the events are applied to the cache.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setSubscriptionAttributes`
+**API:** `org.apache.geode.cache.RegionFactory.setSubscriptionAttributes`
<a id="subscription-attributes__table_63C8ADF9549740BCA4CA8F1CFB7CD75F"></a>
@@ -2173,7 +2173,7 @@ An event-handler plug-in that allows you to program for cache misses. At most, o
For partitioned regions, if you want to have a cache loader, install an instance of the cache loader in every data store. Partitioned regions support partitioned loading, where each cache loader loads only the data entries in the local member. If data redundancy is configured, data is loaded only if the local member holds the primary copy.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCacheLoader`
+**API:** `org.apache.geode.cache.RegionFactory.setCacheLoader`
**Example:**
@@ -2189,7 +2189,7 @@ For partitioned regions, if you want to have a cache loader, install an instance
An event-handler plug-in that allows you to receive before-event notification for changes to the region and its entries. It also has the ability to abort events. At most, one cache writer can be defined in each member for the region. A cache writer may be invoked remotely from other members that have the region defined.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setCacheWriter`
+**API:** `org.apache.geode.cache.RegionFactory.setCacheWriter`
**Example:**
@@ -2207,7 +2207,7 @@ An event-handler plug-in that receives after-event notification of changes to th
Specify the Java class for the cache listener and its initialization parameters with the `<class-name>` and `<parameter>` sub-elements. See [<class-name> and <parameter>](#class-name_parameter).
-**API:** `com.gemstone.gemfire.cache.RegionFactory.addCacheListener`
+**API:** `org.apache.geode.cache.RegionFactory.addCacheListener`
**Example:**
@@ -2244,7 +2244,7 @@ Specifies whether and how to control a region\u2019s size. Size is controlled by re
**Default:** Uses the lru-entry-count algorithm.
-**API:** `com.gemstone.gemfire.cache.RegionFactory.setEvictionAttributes`
+**API:** `org.apache.geode.cache.RegionFactory.setEvictionAttributes`
**Example:**
@@ -2633,7 +2633,7 @@ Defines a region in the cache. See [<region-attributes>](#region-attribute
**Default:**
-**API:** `com.gemstone.gemfire.cache.RegionFactory` or `com.gemstone.gemfire.cache.ClientRegionFactory`
+**API:** `org.apache.geode.cache.RegionFactory` or `org.apache.geode.cache.ClientRegionFactory`
<a id="region__table_4D95B5BF161844CE8DE2E11A3ED40041"></a>
@@ -2674,7 +2674,7 @@ Describes an index to be created on a region. The index node, if any, should all
**Default:**
-**API:** `com.gemstone.gemfire.cache.query.QueryService.createIndex, createKeyIndex, createHashIndex`
+**API:** `org.apache.geode.cache.query.QueryService.createIndex, createKeyIndex, createHashIndex`
<a id="index__table_43625CFF95114DADB2F07052F3743BCC"></a>
@@ -2717,7 +2717,7 @@ An "entry" element describes an entry to be added to a region. Note that if an e
**Default:**
-**API:** `com.gemstone.gemfire.cache.Region.create`, `put`, `get`, `putAll`, `getAll`
+**API:** `org.apache.geode.cache.Region.create`, `put`, `get`, `putAll`, `getAll`
**Example:**
@@ -2768,7 +2768,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<parameter name="cacheserver">
<declarable>
- <class-name>com.gemstone.gemfire.addon.cache.CacheServerInitializer</class-name>
+ <class-name>org.apache.geode.addon.cache.CacheServerInitializer</class-name>
<parameter name="system.property.prefix">
<string>cacheserver</string>
</parameter>
@@ -2811,7 +2811,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<parameter name="cacheserver">
<declarable>
- <class-name>com.gemstone.gemfire.addon.cache.CacheServerInitializer</class-name>
+ <class-name>org.apache.geode.addon.cache.CacheServerInitializer</class-name>
<parameter name="system.property.prefix">
<string>cacheserver</string>
</parameter>
@@ -2854,7 +2854,7 @@ Specify the Java class for the function and its initialization parameters with t
**Default:**
-**API:** `com.gemstone.gemfire.cache.execute.FunctionService`
+**API:** `org.apache.geode.cache.execute.FunctionService`
**Example:**
@@ -2870,7 +2870,7 @@ Specify the Java class for the function and its initialization parameters with t
A memory monitor that tracks cache size as a percentage of total heap or off-heap memory and controls size by restricting access to the cache and prompting eviction of old entries from the cache. For tenured heap, used in conjunction with settings for JVM memory and Java garbage collection. For off-heap memory, used with the off-heap memory manager.
-**API:** `com.gemstone.gemfire.cache.control.ResourceManager`
+**API:** `org.apache.geode.cache.control.ResourceManager`
<a id="resource-manager__table_1132A19E9DC54A67B8C7A625338E346D"></a>
@@ -2956,7 +2956,7 @@ Allows you to configure the DataSerializer for this Geode member. It registers a
Specify the Java class for the `DataSerializer` and its initialization parameters with the `<class-name>` sub-element.
-**API:** You can also register a `DataSerializer` by using the `com.gemstone.gemfire.DataSerializer.register` API. Use the `com.gemstone.gemfire.Instantiator` API to register a `DataSerializable` implementation.
+**API:** You can also register a `DataSerializer` by using the `org.apache.geode.DataSerializer.register` API. Use the `org.apache.geode.Instantiator` API to register a `DataSerializable` implementation.
## <a id="instantiator" class="no-quick-link"></a><instantiator>
@@ -2966,7 +2966,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
**API:** `DataSerializable`
-You can also directly specify `<instantiator>` as a sub-element of `<cache>`. Use the `com.gemstone.gemfire.Instantiator` API to register a `DataSerializable` implementation as the serialization framework for the cache. The following table lists the attribute that can be specified for an `<instantiator>`.
+You can also directly specify `<instantiator>` as a sub-element of `<cache>`. Use the `org.apache.geode.Instantiator` API to register a `DataSerializable` implementation as the serialization framework for the cache. The following table lists the attribute that can be specified for an `<instantiator>`.
<a id="instantiator__table_AEEBB1AB95174276B95861A55C07FBB1"></a>
@@ -3021,7 +3021,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<parameter name="cacheserver">
<declarable>
- <class-name>com.gemstone.gemfire.addon.cache.CacheServerInitializer</class-name>
+ <class-name>org.apache.geode.addon.cache.CacheServerInitializer</class-name>
<parameter name="system.property.prefix">
<string>cacheserver</string>
</parameter>
@@ -3061,7 +3061,7 @@ Specify the Java class and its initialization parameters with the `<class-name>`
``` pre
<parameter name="cacheserver">
<declarable>
- <class-name>com.gemstone.gemfire.addon.cache.CacheServerInitializer</class-name>
+ <class-name>org.apache.geode.addon.cache.CacheServerInitializer</class-name>
<parameter name="system.property.prefix">
<string>cacheserver</string>
</parameter>
[28/50] [abbrv] incubator-geode git commit: Merge remote-tracking
branch 'origin/develop' into feature/IntegratedSecurity
Posted by rv...@apache.org.
Merge remote-tracking branch 'origin/develop' into feature/IntegratedSecurity
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/17399f06
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/17399f06
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/17399f06
Branch: refs/staging/docs-grant1
Commit: 17399f0616c82f8e27b39fcacf5bbd0927d82bf3
Parents: d4c43d3 23e2f5c
Author: Karen Miller <km...@pivotal.io>
Authored: Mon Sep 12 09:53:18 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Mon Sep 12 09:53:18 2016 -0700
----------------------------------------------------------------------
.../managing_data_entries.html.md.erb | 2 +-
.../create_a_region_with_API.html.md.erb | 4 +-
.../managing_data_regions.html.md.erb | 26 ++--
.../data_regions/region_shortcuts.html.md.erb | 6 +-
.../store_retrieve_region_shortcuts.html.md.erb | 2 +-
.../setting_distributed_properties.html.md.erb | 2 +-
.../intro_cache_management.html.md.erb | 10 +-
.../setting_cache_initializer.html.md.erb | 2 +-
.../setting_cache_properties.html.md.erb | 2 +-
.../cluster_config/gfsh_persist.html.md.erb | 2 +-
.../running/running_the_cacheserver.html.md.erb | 6 +-
.../running/running_the_locator.html.md.erb | 8 +-
...implementing_continuous_querying.html.md.erb | 6 +-
.../auto_serialization.html.md.erb | 4 +-
.../jsonformatter_pdxinstances.html.md.erb | 2 +-
.../use_pdx_serializable.html.md.erb | 8 +-
.../use_pdx_serializer.html.md.erb | 10 +-
.../chapter_overview.html.md.erb | 14 +--
.../delta_propagation_example.html.md.erb | 4 +-
.../implementing_delta_propagation.html.md.erb | 4 +-
.../how_distribution_works.html.md.erb | 2 +-
.../locking_in_global_regions.html.md.erb | 4 +-
.../managing_distributed_regions.html.md.erb | 2 +-
.../filtering_multisite_events.html.md.erb | 12 +-
...mplementing_cache_event_handlers.html.md.erb | 10 +-
...ist_of_event_handlers_and_events.html.md.erb | 6 +-
.../resolving_multisite_conflicts.html.md.erb | 2 +-
..._callbacks_that_modify_the_cache.html.md.erb | 4 +-
.../configuring_data_eviction.html.md.erb | 4 +-
.../configuring_data_expiration.html.md.erb | 2 +-
.../function_execution.html.md.erb | 10 +-
.../how_function_execution_works.html.md.erb | 4 +-
.../chapter_overview.html.md.erb | 2 +-
.../implementing_data_loaders.html.md.erb | 4 +-
.../moving_partitioned_data.html.md.erb | 4 +-
...using_custom_partition_resolvers.html.md.erb | 6 +-
.../create_multiple_indexes.html.md.erb | 2 +-
.../querying_basics/running_a_query.html.md.erb | 4 +-
.../dynamic_region_creation.html.md.erb | 42 +++----
.../storing_data_on_disk.html.md.erb | 6 +-
.../transactions/JTA_transactions.html.md.erb | 2 +-
.../transactional_function_example.html.md.erb | 4 +-
.../querying_quick_reference.html.md.erb | 4 +-
getting_started/setup_classpath.html.md.erb | 4 +-
.../disk_store_configuration_params.html.md.erb | 2 +-
managing/heap_use/heap_management.html.md.erb | 4 +-
.../heap_use/off_heap_management.html.md.erb | 2 +-
managing/logging/logging_categories.html.md.erb | 6 +-
managing/logging/logging_whats_next.html.md.erb | 2 +-
.../management/list_of_mbeans_full.html.md.erb | 22 ++--
.../management_system_overview.html.md.erb | 4 +-
managing/management/mm_overview.html.md.erb | 2 +-
.../management/programming_example.html.md.erb | 20 +--
.../performance_controls.html.md.erb | 2 +-
..._controls_controlling_socket_use.html.md.erb | 2 +-
..._controls_setting_cache_timeouts.html.md.erb | 4 +-
.../sockets_and_gateways.html.md.erb | 2 +-
.../region_compression.html.md.erb | 6 +-
.../application_defined_statistics.html.md.erb | 2 +-
.../diagnosing_system_probs.html.md.erb | 22 ++--
.../recovering_from_p2p_crashes.html.md.erb | 2 +-
.../system_failure_and_recovery.html.md.erb | 10 +-
reference/topics/cache_xml.html.md.erb | 110 ++++++++---------
reference/topics/client-cache.html.md.erb | 80 ++++++------
reference/topics/elements_ref.html.md.erb | 8 +-
reference/topics/gfe_cache_xml.html.md.erb | 122 +++++++++----------
...handling_exceptions_and_failures.html.md.erb | 2 +-
.../region_shortcuts_reference.html.md.erb | 8 +-
rest_apps/develop_rest_apps.html.md.erb | 22 ++--
...et_region_data_for_multiple_keys.html.md.erb | 4 +-
rest_apps/get_regions.html.md.erb | 4 +-
rest_apps/post_execute_functions.html.md.erb | 4 +-
rest_apps/post_execute_query.html.md.erb | 6 +-
rest_apps/post_if_absent_data.html.md.erb | 2 +-
.../put_multiple_values_for_keys.html.md.erb | 4 +-
rest_apps/put_replace_data.html.md.erb | 2 +-
rest_apps/put_update_cas_data.html.md.erb | 8 +-
rest_apps/put_update_data.html.md.erb | 2 +-
rest_apps/rest_examples.html.md.erb | 48 ++++----
rest_apps/setup_config.html.md.erb | 2 +-
.../gemcached/deploying_gemcached.html.md.erb | 2 +-
.../gfsh/command-pages/create.html.md.erb | 14 +--
.../gfsh/getting_started_gfsh.html.md.erb | 2 +-
.../changing_gemfire_default_cfg.html.md.erb | 4 +-
.../setting_up_the_module.html.md.erb | 4 +-
.../http_session_mgmt/quick_start.html.md.erb | 4 +-
.../session_state_log_files.html.md.erb | 14 +--
.../tc_setting_up_the_module.html.md.erb | 2 +-
.../tomcat_changing_gf_default_cfg.html.md.erb | 10 +-
.../tomcat_setting_up_the_module.html.md.erb | 14 +--
...weblogic_changing_gf_default_cfg.html.md.erb | 4 +-
.../weblogic_setting_up_the_module.html.md.erb | 8 +-
tools_modules/pulse/quickstart.html.md.erb | 2 +-
.../chapter_overview.html.md.erb | 2 +-
.../client_server_whats_next.html.md.erb | 4 +-
.../using_bind_addresses.html.md.erb | 2 +-
96 files changed, 458 insertions(+), 458 deletions(-)
----------------------------------------------------------------------
[02/50] [abbrv] incubator-geode git commit: fix title containing
angle brackets by quoting it.
Posted by rv...@apache.org.
fix title containing angle brackets by quoting it.
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/62a3bf9e
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/62a3bf9e
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/62a3bf9e
Branch: refs/staging/docs-grant1
Commit: 62a3bf9e5fca987da856b1415a49af1dc72ba82c
Parents: 1218f20
Author: Dave Barnes <db...@pivotal.io>
Authored: Wed Aug 31 14:57:07 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Wed Aug 31 14:57:07 2016 -0700
----------------------------------------------------------------------
reference/topics/client-cache-elements-list.html.md.erb | 2 +-
reference/topics/client-cache.html.md.erb | 11 ++++++-----
2 files changed, 7 insertions(+), 6 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/62a3bf9e/reference/topics/client-cache-elements-list.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/client-cache-elements-list.html.md.erb b/reference/topics/client-cache-elements-list.html.md.erb
index 2b533cc..ee986b3 100644
--- a/reference/topics/client-cache-elements-list.html.md.erb
+++ b/reference/topics/client-cache-elements-list.html.md.erb
@@ -1,5 +1,5 @@
---
-title: <client-cache> Element Hierarchy
+title: "<client-cache> Element Hierarchy"
---
This section shows the hierarchy of `<client-cache>` element sub-elements that you use to configure Geode caches and clients.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/62a3bf9e/reference/topics/client-cache.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/topics/client-cache.html.md.erb b/reference/topics/client-cache.html.md.erb
index bec9d2d..3ae87e0 100644
--- a/reference/topics/client-cache.html.md.erb
+++ b/reference/topics/client-cache.html.md.erb
@@ -1,7 +1,8 @@
+---
+title: "<client-cache> Element Reference"
+---
<a id="cc-client-cache"></a>
-# <client-cache> Element Reference
-
This section documents all `cache.xml` elements that you use to configure Geode clients. All elements are sub-elements of the `<client-cache>` element.
For Geode server configuration, see [<cache> Element Reference](cache_xml.html).
@@ -13,9 +14,9 @@ API: `com.gemstone.gemfire.cache.client.ClientCacheFactory` and `PoolFactory` in
<table>
<caption><span class="tablecap">Table 1. Attributes of <client-cache></span></caption>
<colgroup>
-<col width="33%" />
-<col width="33%" />
-<col width="33%" />
+<col width="25%" />
+<col width="50%" />
+<col width="25%" />
</colgroup>
<thead>
<tr class="header">
[29/50] [abbrv] incubator-geode git commit: Modify gfsh echo examples
to fit better horizontally on a page [#128514629]
Posted by rv...@apache.org.
Modify gfsh echo examples to fit better horizontally
on a page [#128514629]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/f38a81a3
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/f38a81a3
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/f38a81a3
Branch: refs/staging/docs-grant1
Commit: f38a81a37ea4fe3580754f6b69b40cdf27ae0e67
Parents: 23e2f5c
Author: Karen Miller <km...@pivotal.io>
Authored: Mon Sep 12 14:40:50 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Mon Sep 12 14:40:50 2016 -0700
----------------------------------------------------------------------
.../gfsh/command-pages/echo.html.md.erb | 26 ++++++--------------
1 file changed, 7 insertions(+), 19 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/f38a81a3/tools_modules/gfsh/command-pages/echo.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/gfsh/command-pages/echo.html.md.erb b/tools_modules/gfsh/command-pages/echo.html.md.erb
index 9c49a1a..91b775e 100644
--- a/tools_modules/gfsh/command-pages/echo.html.md.erb
+++ b/tools_modules/gfsh/command-pages/echo.html.md.erb
@@ -30,32 +30,20 @@ echo [--string=value]
echo --string="Hello World!"
echo --string="Hello World! This is ${SYS_USER}"
echo --string=${APP_FETCH_SIZE}
+```
+
+To see all the variable set in the shell:
-//To see all the variable set in the shell:
+``` pre
echo --string=$*
```
**Sample Output:**
``` pre
-gfsh>echo --string=$*
- Property | Value
------------------------------- | -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-APP_FETCH_SIZE | 1000
-APP_LAST_EXIT_STATUS | 0
-APP_LOG_FILE | /home/user/gfsh-2013-03-04_12-13-44.log
-APP_NAME | gfsh
-APP_PWD | /home/user
-APP_QUERY_RESULTS_DISPLAY_MODE | table
-APP_QUIET_EXECUTION | false
-SYS_CLASSPATH | /home/user/Pivotal_GemFire_821_b40169/lib/gemfire.jar:/home/user/Pivotal_GemFire_821_b40169/lib/antlr.jar:/home/user/Pivotal_GemFire_821_b40169/lib/gfsh-dependencies.jar:/home/user/Pivotal_GemFire_821_b40169/lib/pulse-dependencies.jar:.:/home/user/Pivotal_GemFire_821_b40169/lib/gemfire.jar:/home/user/Pivotal_GemFire_821_b40169/lib/antlr.jar:/home/user/Pivotal_GemFire_821_b40169/lib/gfSecurityImpl.jar:/home/user/Pivotal_GemFire_821_b40169/lib/jackson-core-asl-1.9.9.jar:/home/user/Pivotal_GemFire_821_b40169/lib/commons-logging.jar:/home/user/Pivotal_GemFire_821_b40169/lib/tomcat-embed-core.jar:/home/user/Pivotal_GemFire_821_b40169/lib/tomcat-embed-logging-juli.jar:/home/user/Pivotal_GemFire_821_b40169/lib/tomcat-embed-jasper.jar:/home/user/Pivotal_GemFire_821_b40169/SampleCode/tutorial/classes:/home/user/Pivotal_GemFire_821_b40169/SampleCode/helloworld/classes:/home/user/Pivotal_GemFire_821_b40169/SampleCode/quickstart/classes:/home/user/Pivotal_GemFir
e_821_b40169/SampleCode/examples/dist/classes:/usr/java/jdk1.8.0_60/jre/../lib/tools.jar
-SYS_GEMFIRE_DIR | /home/user/Pivotal_GemFire_821_b40169
-SYS_HOST_NAME | user
-SYS_JAVA_VERSION | 1.8.0_60
-SYS_OS | Linux
-SYS_OS_LINE_SEPERATOR |
-SYS_USER | user
-SYS_USER_HOME | /home/user
+gfsh>echo --string=${SYS_JAVA_VERSION}
+Post substitution: echo --string=1.8.0_60
+1.8.0_60
```
[05/50] [abbrv] incubator-geode git commit: Put enabling security
into its own section [#129578041]
Posted by rv...@apache.org.
Put enabling security into its own section [#129578041]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/10f9d9a2
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/10f9d9a2
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/10f9d9a2
Branch: refs/staging/docs-grant1
Commit: 10f9d9a2d5d19bc9060c0a8f3080fe837faba7a5
Parents: 6a5c86d
Author: Karen Miller <km...@pivotal.io>
Authored: Wed Aug 31 15:56:00 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Wed Aug 31 15:56:00 2016 -0700
----------------------------------------------------------------------
managing/security/chapter_overview.html.md.erb | 2 +
managing/security/enable_security.html.md.erb | 41 ++++++++++++++++++++
.../implementing_authorization.html.md.erb | 40 -------------------
3 files changed, 43 insertions(+), 40 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/10f9d9a2/managing/security/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/chapter_overview.html.md.erb b/managing/security/chapter_overview.html.md.erb
index b94c66f..da66a96 100644
--- a/managing/security/chapter_overview.html.md.erb
+++ b/managing/security/chapter_overview.html.md.erb
@@ -17,6 +17,8 @@ features help to secure the distributed system.
Apache Geode can authenticate peer system members and clients. It can also authorize cache operations on a server from clients.
+- **[Enable Security with Property Definitions](../../managing/security/enable_security`.html)**
+
- **[Authentication](../../managing/security/authentication_overview.html)**
A distributed system using authentication bars malicious peers or clients, and deters inadvertent access to its cache.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/10f9d9a2/managing/security/enable_security.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/enable_security.html.md.erb b/managing/security/enable_security.html.md.erb
new file mode 100644
index 0000000..b4c1c6b
--- /dev/null
+++ b/managing/security/enable_security.html.md.erb
@@ -0,0 +1,41 @@
+---
+title: Enable Security with Property Definitions
+---
+
+
+The callbacks that implement the authorization of an application
+are specified with the `security-manager` property.
+When this property is defined, authorization is enabled.
+The definition of the `security-manager` property is the
+path to the implementation of the `SecurityManager` interface.
+For example:
+
+``` pre
+security-manager = com.example.security.MySecurityManager
+```
+
+All components of the system invoke the same callback.
+Authorization may be enabled on a component basis with
+the definition of the `security-enabled-components` property.
+Its definition restricts which system components invoke
+the authorization callback.
+
+- `all`. All components invoke the `authorize` callback.
+- `server`.
+- `cluster`.
+- `jmx`. Invokes the `authorize` callback for all components
+that ?
+- `http`.
+- `gateway`.
+
+The `security-enabled-components` property defines
+a comma-separated list of components that will
+invoke the `authorize` callback.
+For example,
+
+``` pre
+security-enabled-components = server, cluster jmx
+```
+``` pre
+security-post-processor = com.example.security.MySecurityPostProcessing
+```
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/10f9d9a2/managing/security/implementing_authorization.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_authorization.html.md.erb b/managing/security/implementing_authorization.html.md.erb
index 30d08af..cf89f24 100644
--- a/managing/security/implementing_authorization.html.md.erb
+++ b/managing/security/implementing_authorization.html.md.erb
@@ -18,46 +18,6 @@ All client operations sent to the server can be authorized. The operations check
All client operations that return a result (like `get` and `query`) and all notifications can also be authorized in the post-operation phase where the callback can peek and even modify the result being sent out.
-## Enable Authorization with Property Definitions
-
-The callbacks that implement the authorization of an application
-are specified with the `security-manager` property.
-When this property is defined, authorization is enabled.
-The definition of the `security-manager` property is the
-path to the implementation of the `SecurityManager` interface.
-For example:
-
-``` pre
-security-manager = com.example.security.MySecurityManager
-```
-
-All components of the system invoke the same callback.
-Authorization may be enabled on a component basis with
-the definition of the `security-enabled-components` property.
-Its definition restricts which system components invoke
-the authorization callback.
-
-- `all`. All components invoke the `authorize` callback.
-- `server`.
-- `cluster`.
-- `jmx`. Invokes the `authorize` callback for all components
-that ?
-- `http`.
-- `gateway`.
-
-The `security-enabled-components` property defines
-a comma-separated list of components that will
-invoke the `authorize` callback.
-For example,
-
-``` pre
-security-enabled-components = server, cluster jmx
-```
-``` pre
-security-post-processor = com.example.security.MySecurityPostProcessing
-```
-
-
## Resource Permissions
## Implement SecurityManager Interface
[44/50] [abbrv] incubator-geode git commit: Clarify "configurations"
in "Region Data Stores and Data Accessors" topic [#130309083]
Posted by rv...@apache.org.
Clarify "configurations" in "Region Data Stores and Data Accessors" topic [#130309083]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/42624de4
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/42624de4
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/42624de4
Branch: refs/staging/docs-grant1
Commit: 42624de4a7747898da69ff702ea242c0117650cd
Parents: e1ffcd1
Author: Dave Barnes <db...@pivotal.io>
Authored: Wed Sep 21 14:58:33 2016 -0700
Committer: Dave Barnes <db...@pivotal.io>
Committed: Wed Sep 21 14:58:33 2016 -0700
----------------------------------------------------------------------
developing/region_options/data_hosts_and_accessors.html.md.erb | 4 ++++
1 file changed, 4 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/42624de4/developing/region_options/data_hosts_and_accessors.html.md.erb
----------------------------------------------------------------------
diff --git a/developing/region_options/data_hosts_and_accessors.html.md.erb b/developing/region_options/data_hosts_and_accessors.html.md.erb
index d57f795..ed167b6 100644
--- a/developing/region_options/data_hosts_and_accessors.html.md.erb
+++ b/developing/region_options/data_hosts_and_accessors.html.md.erb
@@ -7,4 +7,8 @@ Understand the difference between members that store data for a region and membe
<a id="data_hosts_and_accessors__section_0EF33633F97B4C63AC34F523259AD310"></a>
In most cases, when you define a data region in a member\u2019s cache, you also specify whether the member is a data store. Members that store data for a region are referred to as data stores or data hosts. Members that do not store data are referred to as accessor members, or empty members. Any member, store or accessor, that defines a region can access it, put data into it, and receive events from other members. To configure a region so the member is a data accessor, you use configurations that specify no local data storage for the region. Otherwise, the member is a data store for the region.
+For server regions, suppress local data storage at region creation by specifying a region shortcut that contains the term
+"PROXY" in its name, such as `PARTITION_PROXY` or `REPLICATE_PROXY`.
+For client regions, suppress local data storage at region creation by specifying the `PROXY` region
+shortcut. Do not use the `CACHING_PROXY` shortcut for this purpose, as it allows local data storage.
[22/50] [abbrv] incubator-geode git commit: GEODE-37 Package renaming
[#118023839]
Posted by rv...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/session_state_log_files.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/http_session_mgmt/session_state_log_files.html.md.erb b/tools_modules/http_session_mgmt/session_state_log_files.html.md.erb
index 3e925b5..35f849a 100644
--- a/tools_modules/http_session_mgmt/session_state_log_files.html.md.erb
+++ b/tools_modules/http_session_mgmt/session_state_log_files.html.md.erb
@@ -13,23 +13,23 @@ Several log files are written by the various parts of the session management cod
To add Geode-specific FINE logging to the `catalina.log` file, add the following lines to your `<instance>/conf/logging.properties` file:
``` pre
-com.gemstone.gemfire.modules.session.catalina.DeltaSessionManager.level = FINE
-com.gemstone.gemfire.modules.session.catalina.DeltaSession.level = FINE
+org.apache.geode.modules.session.catalina.DeltaSessionManager.level = FINE
+org.apache.geode.modules.session.catalina.DeltaSession.level = FINE
```
These configurations will add FINE logging to the `catalina.DATE.log` file. The following is an example of FINE logging:
``` pre
-06-Sep-2011 15:59:47.250 FINE com.gemstone.gemfire.modules.session.catalina.DeltaSessionManager.start
+06-Sep-2011 15:59:47.250 FINE org.apache.geode.modules.session.catalina.DeltaSessionManager.start
DeltaSessionManager[container=StandardEngine[Catalina].StandardHost[localhost].StandardContext[/manager];
regionName=gemfire_modules_sessions; regionAttributesId=PARTITION_REDUNDANT]: Starting
-06-Sep-2011 15:59:47.254 FINE com.gemstone.gemfire.modules.session.catalina.DeltaSessionManager.registerJvmRouteBinderValve
+06-Sep-2011 15:59:47.254 FINE org.apache.geode.modules.session.catalina.DeltaSessionManager.registerJvmRouteBinderValve
DeltaSessionManager[container=StandardEngine[Catalina].StandardHost[localhost].StandardContext[/manager];
regionName=gemfire_modules_sessions; regionAttributesId=PARTITION_REDUNDANT]: Registering JVM route binder valve
-06-Sep-2011 15:59:47.351 FINE com.gemstone.gemfire.modules.session.catalina.ClientServerSessionCache.createOrRetrieveRegion
-Created session region: com.gemstone.gemfire.internal.cache.LocalRegion[path='/gemfire_modules_sessions';
+06-Sep-2011 15:59:47.351 FINE org.apache.geode.modules.session.catalina.ClientServerSessionCache.createOrRetrieveRegion
+Created session region: org.apache.geode.internal.cache.LocalRegion[path='/gemfire_modules_sessions';
scope=LOCAL';dataPolicy=EMPTY; gatewayEnabled=false]
```
@@ -77,7 +77,7 @@ To add fine-level logging to the Geode Cache Client, add the 'log-level' propert
``` pre
<Listener log-level="fine"
cache-xml-file="${geode-cs.cache.configuration.file}"
-className="com.gemstone.gemfire.modules.session.catalina.ClientServerCacheLifecycleListener"
+className="org.apache.geode.modules.session.catalina.ClientServerCacheLifecycleListener"
criticalHeapPercentage="${geode-cs.critical.heap.percentage}"
evictionHeapPercentage="${geode-cs.eviction.heap.percentage}"
log-file="${geode-cs.log.file}"
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/tc_setting_up_the_module.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/http_session_mgmt/tc_setting_up_the_module.html.md.erb b/tools_modules/http_session_mgmt/tc_setting_up_the_module.html.md.erb
index f12d4b2..538f40d 100644
--- a/tools_modules/http_session_mgmt/tc_setting_up_the_module.html.md.erb
+++ b/tools_modules/http_session_mgmt/tc_setting_up_the_module.html.md.erb
@@ -89,7 +89,7 @@ Geode session state management provides its own clustering functionality. If you
To verify that the system is running, check the log file for a message similar to:
``` pre
-Mar 29, 2016 8:38:31 AM com.gemstone.gemfire.modules.session.bootstrap.AbstractCache
+Mar 29, 2016 8:38:31 AM org.apache.geode.modules.session.bootstrap.AbstractCache
lifecycleEvent
INFO: Initializing GemFire Modules
Modules version: 1.0.0-incubating.M2-SNAPSHOT
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/tomcat_changing_gf_default_cfg.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/http_session_mgmt/tomcat_changing_gf_default_cfg.html.md.erb b/tools_modules/http_session_mgmt/tomcat_changing_gf_default_cfg.html.md.erb
index 65ab2c8..809ea73 100644
--- a/tools_modules/http_session_mgmt/tomcat_changing_gf_default_cfg.html.md.erb
+++ b/tools_modules/http_session_mgmt/tomcat_changing_gf_default_cfg.html.md.erb
@@ -20,7 +20,7 @@ Geode system properties must be set by adding properties to Tomcat's `server.xml
``` pre
<Listener
- className="com.gemstone.gemfire.modules.session.catalina.xxxLifecycleListener"
+ className="org.apache.geode.modules.session.catalina.xxxLifecycleListener"
name="value"
name="value"
...
@@ -31,7 +31,7 @@ If the `xxxLifecycleListener` is a `PeerToPeerCacheLifecycleListener`, then a mi
``` pre
<Listener
- className="com.gemstone.gemfire.modules.session.catalina.
+ className="org.apache.geode.modules.session.catalina.
PeerToPeerCacheLifecycleListener"
cache-xml-file="cache-peer.xml"
locators="localhost[10334]"
@@ -66,7 +66,7 @@ To edit Geode cache properties such as the name and the characteristics of the c
``` pre
<Manager
- className="com.gemstone.gemfire.modules.session.catalina.Tomcat7DeltaSessionManager"
+ className="org.apache.geode.modules.session.catalina.Tomcat7DeltaSessionManager"
name="value"
name="value"
...
@@ -76,7 +76,7 @@ To edit Geode cache properties such as the name and the characteristics of the c
In the preceding code snippet, `name` is the property name and `value` is the property value. For example:
``` pre
-<Manager className="com.gemstone.gemfire.modules.session.catalina.
+<Manager className="org.apache.geode.modules.session.catalina.
Tomcat7DeltaSessionManager"
regionAttributesId="PARTITION_REDUNDANT"
regionName="my_region"
@@ -95,7 +95,7 @@ Default: Set
To disable this configuration, remove or comment out the following line from Tomcat's `context.xml` file.
``` pre
-<Valve className="com.gemstone.gemfire.modules.session.catalina.CommitSessionValve"/>
+<Valve className="org.apache.geode.modules.session.catalina.CommitSessionValve"/>
```
<dt>**enableDebugListener**</dt>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb b/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
index 780b311..a94609e 100644
--- a/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
+++ b/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
@@ -12,7 +12,7 @@ Configuration is slightly different depending on the topology you are setting up
To run Geode in a peer-to-peer configuration, add the following line to Tomcat's `$CATALINA_HOME$/conf/server.xml` within the `<Server>` tag:
``` pre
-<Listener className="com.gemstone.gemfire.modules.session.catalina.
+<Listener className="org.apache.geode.modules.session.catalina.
PeerToPeerCacheLifecycleListener"
locators="localhost[10334]" />
```
@@ -22,14 +22,14 @@ Depending on the version of Tomcat you are using, add one of the following lines
For Tomcat 6.0:
``` pre
-<Manager className="com.gemstone.gemfire.modules.session.catalina.
+<Manager className="org.apache.geode.modules.session.catalina.
Tomcat6DeltaSessionManager"/>
```
For Tomcat 7.0 and above:
``` pre
-<Manager className="com.gemstone.gemfire.modules.session.catalina.
+<Manager className="org.apache.geode.modules.session.catalina.
Tomcat7DeltaSessionManager"/>
```
@@ -40,7 +40,7 @@ For Tomcat 7.0 and above:
To run Geode in a client/server configuration, the application server will operate as a Geode client. To do this, add the following line to `$CATALINA_HOME$/conf/server.xml` within the `<Server>` tag:
``` pre
-<Listener className="com.gemstone.gemfire.modules.session.catalina.
+<Listener className="org.apache.geode.modules.session.catalina.
ClientServerCacheLifecycleListener"/>
```
@@ -49,14 +49,14 @@ Depending on the version of Tomcat you are using, add one of the following lines
For Tomcat 6.0:
``` pre
-<Manager className="com.gemstone.gemfire.modules.session.catalina.
+<Manager className="org.apache.geode.modules.session.catalina.
Tomcat6DeltaSessionManager"/>
```
For Tomcat 7.0 and above:
``` pre
-<Manager className="com.gemstone.gemfire.modules.session.catalina.
+<Manager className="org.apache.geode.modules.session.catalina.
Tomcat7DeltaSessionManager"/>
```
@@ -93,7 +93,7 @@ You can verify that Geode has successfully started by inspecting the Tomcat log
``` pre
Nov 8, 2010 12:12:12 PM
-com.gemstone.gemfire.modules.session.catalina.ClientServerCacheLifecycleListener
+org.apache.geode.modules.session.catalina.ClientServerCacheLifecycleListener
createOrRetrieveCache
INFO: Created GemFireCache[id = 2066231378; isClosing = false;
created = Mon Nov 08 12:12:12 PDT 2010; server = false;
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb b/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb
index cf45c71..d86dca6 100644
--- a/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb
+++ b/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb
@@ -30,7 +30,7 @@ To edit Geode system properties, you must add properties to Geode Session Filter
<filter>
<filter-name>gemfire-session-filter</filter-name>
<filter-class>
- com.gemstone.gemfire.modules.session.filter.SessionCachingFilter
+ org.apache.geode.modules.session.filter.SessionCachingFilter
</filter-class>
<init-param>
<param-name>cache-type</param-name>
@@ -82,7 +82,7 @@ To edit Geode cache properties (such as the name and the characteristics of the
<filter>
<filter-name>gemfire-session-filter</filter-name>
<filter-class>
- com.gemstone.gemfire.modules.session.filter.SessionCachingFilter
+ org.apache.geode.modules.session.filter.SessionCachingFilter
</filter-class>
<init-param>
<param-name>cache-type</param-name>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb b/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
index 77de1c8..935853f 100644
--- a/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
+++ b/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
@@ -20,7 +20,7 @@ To modify your war or ear file manually, make the following updates:
<filter>
<filter-name>gemfire-session-filter</filter-name>
<filter-class>
- com.gemstone.gemfire.modules.session.filter.SessionCachingFilter
+ org.apache.geode.modules.session.filter.SessionCachingFilter
</filter-class>
<init-param>
<param-name>cache-type</param-name>
@@ -40,7 +40,7 @@ To modify your war or ear file manually, make the following updates:
<dispatcher>ERROR</dispatcher>
</filter-mapping>
<listener>
- <listener-class>com.gemstone.gemfire.modules.session.filter.SessionListener</listener-class>
+ <listener-class>org.apache.geode.modules.session.filter.SessionListener</listener-class>
</listener>
```
@@ -100,7 +100,7 @@ to result in the following `web.xml` content:
<filter>
<filter-name>gemfire-session-filter</filter-name>
<filter-class>
- com.gemstone.gemfire.modules.session.filter.SessionCachingFilter
+ org.apache.geode.modules.session.filter.SessionCachingFilter
</filter-class>
<init-param>
<param-name>cache-type</param-name>
@@ -127,7 +127,7 @@ to result in the following `web.xml` content:
<filter>
<filter-name>gemfire-session-filter</filter-name>
<filter-class>
- com.gemstone.gemfire.modules.session.filter.SessionCachingFileter
+ org.apache.geode.modules.session.filter.SessionCachingFileter
</filter-class>
<init-param>
<param-name>cache-type</param-name>
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/pulse/quickstart.html.md.erb
----------------------------------------------------------------------
diff --git a/tools_modules/pulse/quickstart.html.md.erb b/tools_modules/pulse/quickstart.html.md.erb
index a452703..22e5b16 100644
--- a/tools_modules/pulse/quickstart.html.md.erb
+++ b/tools_modules/pulse/quickstart.html.md.erb
@@ -771,7 +771,7 @@ The Pulse Data Browser enables you to query region data. Note that there are two
- `QueryResultSetLimit` limits the number of rows that Data Browser queries return. 1000 rows are displayed by default.
- `QueryCollectionsDepth` limits the number of elements of a collection that Data Browser queries return. This attribute applies to query results contain collections such as Map, List, and so forth. The default value is 100 elements.
-See the `com.gemstone.gemfire.management.DistributedSystemMXBean` JavaDocs for information on available MBean methods and attributes.
+See the `org.apache.geode.management.DistributedSystemMXBean` JavaDocs for information on available MBean methods and attributes.
The following shows an example Data Browser view:
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/topologies_and_comm/cs_configuration/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/topologies_and_comm/cs_configuration/chapter_overview.html.md.erb b/topologies_and_comm/cs_configuration/chapter_overview.html.md.erb
index cacc77e..6fd6574 100644
--- a/topologies_and_comm/cs_configuration/chapter_overview.html.md.erb
+++ b/topologies_and_comm/cs_configuration/chapter_overview.html.md.erb
@@ -30,6 +30,6 @@ In the client/server architecture, a relatively small server farm manages the ca
- **[Fine-Tuning Your Client/Server Configuration](../../topologies_and_comm/cs_configuration/client_server_whats_next.html)**
- You can fine-tune your client/server system with server load-balancing and client thread use of pool connections. For example, you can configure how often the servers check their load with the cache server `load-poll-interval` property, or configure your own server load metrics by implementing the `com.gemstone.gemfire.cache.server` package.
+ You can fine-tune your client/server system with server load-balancing and client thread use of pool connections. For example, you can configure how often the servers check their load with the cache server `load-poll-interval` property, or configure your own server load metrics by implementing the `org.apache.geode.cache.server` package.
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/topologies_and_comm/cs_configuration/client_server_whats_next.html.md.erb
----------------------------------------------------------------------
diff --git a/topologies_and_comm/cs_configuration/client_server_whats_next.html.md.erb b/topologies_and_comm/cs_configuration/client_server_whats_next.html.md.erb
index 1adcf08..2cd802b 100644
--- a/topologies_and_comm/cs_configuration/client_server_whats_next.html.md.erb
+++ b/topologies_and_comm/cs_configuration/client_server_whats_next.html.md.erb
@@ -2,7 +2,7 @@
title: Fine-Tuning Your Client/Server Configuration
---
-You can fine-tune your client/server system with server load-balancing and client thread use of pool connections. For example, you can configure how often the servers check their load with the cache server `load-poll-interval` property, or configure your own server load metrics by implementing the `com.gemstone.gemfire.cache.server` package.
+You can fine-tune your client/server system with server load-balancing and client thread use of pool connections. For example, you can configure how often the servers check their load with the cache server `load-poll-interval` property, or configure your own server load metrics by implementing the `org.apache.geode.cache.server` package.
## <a id="client_server_whats_next__section_64AD4CBC253B4C309E3D592D0CED2A6B" class="no-quick-link"></a>How Server Load Conditioning Works
@@ -17,7 +17,7 @@ Geode provides a default utility that probes the server and its resource usage t
- The pool connection load is the number of connections to the server divided by the server\u2019s `max-connections` setting. This means that servers with a lower `max-connections` setting receives fewer connections than servers with a higher setting. The load is a number between 0 and 1, where 0 means there are no connections, and 1 means the server is at `max-connections`. The load estimate for each additional pool connection is 1/`max-connections`.
- The subscription connection load is the number of subscription queues hosted by this server. The load estimate for each additional subscription connection is 1.
-To use your own server load metrics instead of the default, implement the `ServerLoadProbe` or `ServerLoadProbeAdapter` and related interfaces and classes in the `com.gemstone.gemfire.cache.server` package. The load for each server is weighed relative to the loads reported by other servers in the system.
+To use your own server load metrics instead of the default, implement the `ServerLoadProbe` or `ServerLoadProbeAdapter` and related interfaces and classes in the `org.apache.geode.cache.server` package. The load for each server is weighed relative to the loads reported by other servers in the system.
## <a id="client_server_whats_next__section_CE66DA4747BC4870893DB93690DAB95B" class="no-quick-link"></a>Client Thread Use of Pool Connections
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb
----------------------------------------------------------------------
diff --git a/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb b/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb
index 19458a3..617bfdd 100644
--- a/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb
+++ b/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb
@@ -90,6 +90,6 @@ Set the locator bind address using one of these methods:
- Inside a Geode application, take one of the following actions:
- Automatically start a co-located locator using the gemfire property `start-locator`, and specifying the bind address for it in that property setting.
- - Use `com.gemstone.gemfire.distributed.LocatorLauncher` API to start the locator inside your code. Use the `LocatorLauncher.Builder` class to construct an instance of the `LocatorLauncher`, use the `setBindAddress` method to specify the IP address to use and then use the start() method to start a Locator service embedded in your Java application process.
+ - Use `org.apache.geode.distributed.LocatorLauncher` API to start the locator inside your code. Use the `LocatorLauncher.Builder` class to construct an instance of the `LocatorLauncher`, use the `setBindAddress` method to specify the IP address to use and then use the start() method to start a Locator service embedded in your Java application process.
If your locator uses a bind address, make sure every process that accesses the locator has the address as well. For peer-to-peer access to the locator, use the locator's bind address and the locator's port in your `gemfire.properties` `locators` list. For server discovery in a client/server installation, use the locator's bind address and the locator's port in the locator list you provide to in the client\u2019s server pool configuration.
[16/50] [abbrv] incubator-geode git commit: Use some em dashes to
improve a page's appearance. [#129578041]
Posted by rv...@apache.org.
Use some em dashes to improve a page's appearance. [#129578041]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/c9f6f0db
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/c9f6f0db
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/c9f6f0db
Branch: refs/staging/docs-grant1
Commit: c9f6f0dbe0900372378f6fdea478fabbd0bdc57d
Parents: 0ce38b1
Author: Karen Miller <km...@pivotal.io>
Authored: Tue Sep 6 17:36:55 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Tue Sep 6 17:36:55 2016 -0700
----------------------------------------------------------------------
managing/security/enable_security.html.md.erb | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/c9f6f0db/managing/security/enable_security.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/enable_security.html.md.erb b/managing/security/enable_security.html.md.erb
index b281ea9..441b66c 100644
--- a/managing/security/enable_security.html.md.erb
+++ b/managing/security/enable_security.html.md.erb
@@ -26,17 +26,17 @@ Its definition restricts which system components invoke
the authentication and authorization callbacks.
The defined values for system components:
-- `all`. All components invoke the security callbacks.
-- `server`. Invokes security callbacks upon connection and operation
+- `all`—All components invoke the security callbacks.
+- `server`—Invokes security callbacks upon connection and operation
requests that a client makes of a server.
-- `cluster`. Invokes security callbacks upon connection and operation
+- `cluster`—Invokes security callbacks upon connection and operation
requests that a server makes as the peer of a locator.
-- `jmx`. Invokes security callbacks upon connection and operation
+- `jmx`—Invokes security callbacks upon connection and operation
requests that components communicating with a JMX manager make of a locator.
Both `gfsh` and `Pulse` use this form of communication.
-- `http`. Invokes security callbacks upon connection and operation
+- `http`—Invokes security callbacks upon connection and operation
requests that applications communicating via the REST API make of a server.
-- `gateway`. Invokes security callbacks upon connection and operation
+- `gateway`—Invokes security callbacks upon connection and operation
requests that a gateway sender makes of a locator.
The `security-enabled-components` property defines
[21/50] [abbrv] incubator-geode git commit: Initial contents for
authentication using new integrated security. [#129183221]
Posted by rv...@apache.org.
Initial contents for authentication using new integrated
security. [#129183221]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/f778e4a3
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/f778e4a3
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/f778e4a3
Branch: refs/staging/docs-grant1
Commit: f778e4a393ac7a59c2d0056c09872b057f6e0260
Parents: 4ad23a1
Author: Karen Miller <km...@pivotal.io>
Authored: Thu Sep 8 14:25:48 2016 -0700
Committer: Karen Miller <km...@pivotal.io>
Committed: Thu Sep 8 14:25:48 2016 -0700
----------------------------------------------------------------------
.../authentication_overview.html.md.erb | 6 +-
.../implementing_authentication.html.md.erb | 84 ++++++--------------
2 files changed, 29 insertions(+), 61 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/f778e4a3/managing/security/authentication_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/authentication_overview.html.md.erb b/managing/security/authentication_overview.html.md.erb
index 8ab3558..ad3af66 100644
--- a/managing/security/authentication_overview.html.md.erb
+++ b/managing/security/authentication_overview.html.md.erb
@@ -2,11 +2,13 @@
title: Authentication
---
-A distributed system using authentication verifies the identities of peers, clients, and and other communicating entities.
+Authentication verifies the identities of components within the distributed
+system such as peers, clients, and those connecting to a JMX manager.
- **[Implementing Authentication](../../managing/security/implementing_authentication.html)**
- Apache Geode provides a flexible framework for your security authentication plug-ins. You choose the method of authentication, such as LDAP or PKCS, and program the plug-ins accordingly.
+ All components of the distributed system authenticate the same way,
+ through a custom-written method.
- **[Encrypting Passwords for Use in cache.xml](../../managing/security/encrypting_passwords.html)**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/f778e4a3/managing/security/implementing_authentication.html.md.erb
----------------------------------------------------------------------
diff --git a/managing/security/implementing_authentication.html.md.erb b/managing/security/implementing_authentication.html.md.erb
index e7ae1d1..9bbb9d3 100644
--- a/managing/security/implementing_authentication.html.md.erb
+++ b/managing/security/implementing_authentication.html.md.erb
@@ -2,69 +2,35 @@
title: Implementing Authentication
---
-Apache Geode provides a flexible framework for your security authentication plug-ins. You choose the method of authentication, such as LDAP or PKCS, and program the plug-ins accordingly.
+Authentication lends a measure of security to a distributed system
+by verifying the identity of components as they connect to the system.
+All components use the same authentication mechanism.
## How Authentication Works
-Joining members provide credentials to existing members who check the credentials and either reject the joining member or approve it.
+When a component initiates a connection to the distributed system,
+the `SecurityManager.authenticate` method is invoked.
+The component provides credentials in the form of `Properties`,
+which are passed to the `authenticate` method.
+The `authenticate` method is expected to either return an object
+representing a principal or throw an `AuthenticationFailedException`.
-If approved, the connection request returns a `java.security.Principal` object, used to identify the member in future operations.
-
-- Joining peer members are authenticated by the locator to which they connect.
-- Clients are authenticated by their server during the connection initialization and for each operation request.
-- Servers may be authenticated by their clients during the connection initialization.
-- Depending on the member, the new member may in turn become an authenticator to other joining members. Members joining a system must trust that existing members are already authenticated.
-
-Locators maintain and distribute the authenticated member list. The distributed member list is also authenticated by all members, which prevents an unauthorized application from introducing itself into membership by distributing a member list that includes itself.
-
-<img src="../../images/security-1.gif" id="how_authentication_works__image_D3AE53AB4E0441A5A078E5D07EC20C5D" class="image" />
-
-Geode authentication provides a flexible plug-in framework. Any security infrastructure can be plugged in to the system as long as the plug-ins implement the required Geode interfaces.
-## Enable Authentication with Property Definitions
## Implement SecurityManager Interface
-## <a id="implementing_authentication__section_0ECD014AA498429FA72B1DB8FB9C040B" class="no-quick-link"></a>Locators That Require Authentication
-
-Colocated locators, such as those started with the LocatorLauncher API, do not require security settings because they do not join the distributed system as individual members.
-
-All other standalone locators, including those started with the `gfsh start locator` command must be configured with the correct security settings.
-
-## <a id="how_authentication_works__section_3C5F1D7D27CC4C85B01F6F91AA602ED6" class="no-quick-link"></a>Client Authentication Options
-
-The Geode client can connect in two different ways:
-
-1. **Process level**. Each pool creates a configured minimum number of connections across the server group. The pool accesses the least loaded server for each cache operation. This type of connection is required. Process level connections represent the overall client process and are the default way a client accesses the server cache.
-2. **User level**. Each client user/pool pair creates a connection to one server and then sticks with it for operations. If the server is unable to respond to a request, the pool selects a new one for the user. This type of connection is created *from* the process level connection. These connections represent individual users established within the client process. These connections are generally used by application servers or web servers that act as clients to Geode servers. A single application or web server process can service a large number of users, each with their own unique identification and with varied access permissions.
-
-By default, the server pools in clients use process level authentication. You can enable user level authentication by setting the pool\u2019s multiuser-authentication attribute to true. Process level and user level pools can be used inside one client if needed.
-
-<img src="../../images/security-3.gif" id="how_authentication_works__image_A16EEDE08B0D480187F1C757E6A31140" class="image" />
-
-## <a id="how_authentication_works__section_79E28941E4A74318AF3B4B85525F9CA9" class="no-quick-link"></a>Client Authentication Process
-
-The client authentication process occurs for each connection established by a pool, regardless of whether the pool is configured for process-wide or single user connections. All credentials are checked for each connection between client and server, including the server-to-client notification channel.
-
-1. When the client requests a new connection:
- 1. The server authenticates the client\u2019s credentials and assigns it an internal principal, used to authorize client operations in the server cache
- 2. The server generates a random unique identifier and returns it to the client to use in its next request
-
-2. For each operation request after the initial connection is established:
- 1. The client sends the request with the unique identifier it received from the server in the last communication.
- 2. The server verifies the identifier and processes the request, then responds with a new randomly generated unique identifier, for the client to include in its next request.
-
-This ever-changing identifier provides protection against replay attacks, because each client request must include the unique identifier. The server never processes the same request twice. For the most secure communication, add encryption, like Diffie-Hellman.
-
-If the connection fails after the client has sent a request and before the server can respond, the next server request fails due to an invalid unique identifier, and the client pool automatically establishes a new connection to the server system for the client.
-
-## <a id="how_authentication_works__section_05201B3F7B8D466C97EEE5235C749984" class="no-quick-link"></a>When a Member Fails to Join
-
-The following describe the scenarios that occur when a member fails to join:
-
-- Peer credentials are initialized and verified automatically when a member joins a distributed system.
- - If a joining member has invalid credentials, the `CacheFactory.create` method throws an `AuthenticationFailedException`.
- - If a joining member does not provide credentials, the request throws an `AuthenticationRequiredException`.
-- Client credentials are initialized and verified automatically during the initial connection process.
- - If client authentication fails due to invalid credentials, the server sends an `AUTHENTICATION_FAILED` message back to the client. The client handshake fails, and an `AuthenticationFailedException` is thrown for the current operation.
- - If the client authentication fails due to missing credentials, the server sends a `NO_AUTHENTICATION` message back to the client. The client connection fails, and an `AuthenticationRequiredException` is thrown for the current operation.
-
+Complete these items to implement authentication.
+
+- Decide upon an authentication algorithm.
+The [Authentication Example](authentication_examples.html)
+stores a set of user name and
+password pairs that represent the identities of components
+that will connect to the system.
+This simplistic algorithm returns the user name as a principal
+if the user name and password passed to the `authenticate` method
+are a match for one of the stored pairs.
+- Define the `security-manager` and `security-enabled-components` properties.
+See [Enable Security with Property Definitions](enable_security.html)
+for details about these properties.
+- Implement the `authenticate` method of the `SecurityManager` interface.
+- Define any extra resources that the implemented authentication algorithm
+needs in order to make a decision.