geode-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@apache.org
Subject [22/50] [abbrv] incubator-geode git commit: GEODE-37 Package renaming [#118023839]
Date Fri, 30 Sep 2016 00:42:38 GMT
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’s
`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’s server pool configuration.


Mime
View raw message