ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sboi...@apache.org
Subject [5/6] incubator-ignite git commit: #ignite-164: Change GridGain to Ignite in comments.
Date Wed, 04 Feb 2015 17:27:11 GMT
http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifyInput.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifyInput.java b/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifyInput.java
index 776b6a0..3d9ba04 100644
--- a/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifyInput.java
+++ b/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifyInput.java
@@ -32,7 +32,7 @@ import java.lang.annotation.*;
  * <li>java array</li>
  * </ul>
  * If grid-enabled method contains several parameters with types described above
- * then GridGain searches for parameters with {@link GridifyInput} annotation.
+ * then Ignite searches for parameters with {@link GridifyInput} annotation.
  * <b>Only one</b> method parameter with {@link GridifyInput} annotation allowed.
  * @see GridifySetToValue
  * @see GridifySetToSet

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToSet.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToSet.java b/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToSet.java
index 11ef0d7..889b2f9 100644
--- a/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToSet.java
+++ b/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToSet.java
@@ -66,7 +66,7 @@ import java.lang.annotation.*;
  * then you must implement custom grid task which will take care of proper state
  * initialization (see
  * <a target="github" href="https://github.com/gridgain/gridgain/tree/master/examples/java/org/gridgain/examples/helloworld/gridify/state">HelloWorld - Gridify With State</a>
- * example). In either case, GridGain must be able to serialize the state passed to remote node.
+ * example). In either case, Ignite must be able to serialize the state passed to remote node.
  * <p>
  * <h1 class="header">Java Example</h1>
  * <p>
@@ -95,7 +95,7 @@ import java.lang.annotation.*;
  * <p>
  * <h1 class="header">Jboss AOP</h1>
  * The following configuration needs to be applied to enable JBoss byte code
- * weaving. Note that GridGain is not shipped with JBoss and necessary
+ * weaving. Note that Ignite is not shipped with JBoss and necessary
  * libraries will have to be downloaded separately (they come standard
  * if you have JBoss installed already):
  * <ul>
@@ -172,16 +172,16 @@ public @interface GridifySetToSet {
      * be the sub-collection
      * that will travel to remote nodes. Note that this is NOT a dynamic setting and you have to set
      * the split size up front. This may look
-     * as a deficiency but GridGain will properly handle this case by giving more than one sub-collection
+     * as a deficiency but Ignite will properly handle this case by giving more than one sub-collection
      * to a specific node (as defined by load balancing SPI in use).
      * <p>
      * This value should be greater than zero and can be less, equal or greater than {@link #threshold()}
      * value. In most cases, however, the optimal value for the split size is the {@link #threshold()} value.
-     * For example, if input collection size is 100, number of nodes 10 and split size is set to 5 - GridGain
+     * For example, if input collection size is 100, number of nodes 10 and split size is set to 5 - Ignition
      * will submit 2 sub-collections of 5 elements each to each node (provided in order by load
      * balancing SPI).
      * <p>
-     * By default (when split size is zero) - GridGain will automatically determine the split size based on
+     * By default (when split size is zero) - Ignite will automatically determine the split size based on
      * number of nodes and collection size - if collection size is available (not an iterator). If collection
      * size cannot be determined - the split size will default to threshold. If threshold is not set - a runtime
      * exception will be thrown.

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToValue.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToValue.java b/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToValue.java
index 3a77af2..5927bd5 100644
--- a/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToValue.java
+++ b/modules/core/src/main/java/org/apache/ignite/compute/gridify/GridifySetToValue.java
@@ -66,7 +66,7 @@ import java.lang.annotation.*;
  * then you must implement custom grid task which will take care of proper state
  * initialization (see
  * <a target="github" href="https://github.com/gridgain/gridgain/tree/master/examples/java/org/gridgain/examples/helloworld/gridify/state">HelloWorld - Gridify With State</a>
- * example). In either case, GridGain must be able to serialize the state passed to remote node.
+ * example). In either case, Ignite must be able to serialize the state passed to remote node.
  * <p>
  * <h1 class="header">Java Example</h1>
  * <p>
@@ -93,7 +93,7 @@ import java.lang.annotation.*;
  * <p>
  * <h1 class="header">Jboss AOP</h1>
  * The following configuration needs to be applied to enable JBoss byte code
- * weaving. Note that GridGain is not shipped with JBoss and necessary
+ * weaving. Note that Ignite is not shipped with JBoss and necessary
  * libraries will have to be downloaded separately (they come standard
  * if you have JBoss installed already):
  * <ul>
@@ -170,16 +170,16 @@ public @interface GridifySetToValue {
      * be the sub-collection
      * that will travel to remote nodes. Note that this is NOT a dynamic setting and you have to set
      * the split size up front. This may look
-     * as a deficiency but GridGain will properly handle this case by giving more than one sub-collection
+     * as a deficiency but Ignite will properly handle this case by giving more than one sub-collection
      * to a specific node (as defined by load balancing SPI in use).
      * <p>
      * This value should be greater than zero and can be less, equal or greater than {@link #threshold()}
      * value. In most cases, however, the optimal value for the split size is the {@link #threshold()} value.
-     * For example, if input collection size is 100, number of nodes 10 and split size is set to 5 - GridGain
+     * For example, if input collection size is 100, number of nodes 10 and split size is set to 5 - Ignition
      * will submit 2 sub-collections of 5 elements each to each node (provided in order by load
      * balancing SPI).
      * <p>
-     * By default (when split size is zero) - GridGain will automatically determine the split size based on
+     * By default (when split size is zero) - Ignite will automatically determine the split size based on
      * number of nodes and collection size - if collection size is available (not an iterator). If collection
      * size cannot be determined - the split size will default to threshold. If threshold is not set - a runtime
      * exception will be thrown.

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/configuration/ClientConnectionConfiguration.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/configuration/ClientConnectionConfiguration.java b/modules/core/src/main/java/org/apache/ignite/configuration/ClientConnectionConfiguration.java
index d85b036..14650d6 100644
--- a/modules/core/src/main/java/org/apache/ignite/configuration/ClientConnectionConfiguration.java
+++ b/modules/core/src/main/java/org/apache/ignite/configuration/ClientConnectionConfiguration.java
@@ -151,7 +151,7 @@ public class ClientConnectionConfiguration {
     /**
      * Sets path, either absolute or relative to {@code IGNITE_HOME}, to {@code JETTY}
      * XML configuration file. {@code JETTY} is used to support REST over HTTP protocol for
-     * accessing GridGain APIs remotely.
+     * accessing Ignite APIs remotely.
      *
      * @param jettyPath Path to {@code JETTY} XML configuration file.
      */
@@ -162,7 +162,7 @@ public class ClientConnectionConfiguration {
     /**
      * Gets path, either absolute or relative to {@code IGNITE_HOME}, to {@code Jetty}
      * XML configuration file. {@code Jetty} is used to support REST over HTTP protocol for
-     * accessing GridGain APIs remotely.
+     * accessing Ignite APIs remotely.
      * <p>
      * If not provided, Jetty instance with default configuration will be started picking
      * {@link org.apache.ignite.IgniteSystemProperties#IGNITE_JETTY_HOST} and {@link org.apache.ignite.IgniteSystemProperties#IGNITE_JETTY_PORT}
@@ -534,8 +534,8 @@ public class ClientConnectionConfiguration {
      * Shutdown flag for REST executor service.
      * <p>
      * If not provided, default value {@code true} will be used which will shutdown
-     * executor service when GridGain stops regardless whether it was started before GridGain
-     * or by GridGain.
+     * executor service when Ignite stops regardless whether it was started before Ignition
+     * or by Ignition.
      *
      * @return REST executor service shutdown flag.
      */

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/configuration/IgniteAddressResolver.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/configuration/IgniteAddressResolver.java b/modules/core/src/main/java/org/apache/ignite/configuration/IgniteAddressResolver.java
index 7c40621..a736f44 100644
--- a/modules/core/src/main/java/org/apache/ignite/configuration/IgniteAddressResolver.java
+++ b/modules/core/src/main/java/org/apache/ignite/configuration/IgniteAddressResolver.java
@@ -26,7 +26,7 @@ import java.util.*;
  * Provides resolution between external and internal addresses. In some cases
  * network routers are configured to perform address mapping between external
  * and internal networks and the same mapping must be available to SPIs
- * in GridGain that perform communication over IP protocols.
+ * in Ignite that perform communication over IP protocols.
  */
 public interface IgniteAddressResolver {
     /**

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/configuration/IgniteConfiguration.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/configuration/IgniteConfiguration.java b/modules/core/src/main/java/org/apache/ignite/configuration/IgniteConfiguration.java
index 2698ae1..92c6b48 100644
--- a/modules/core/src/main/java/org/apache/ignite/configuration/IgniteConfiguration.java
+++ b/modules/core/src/main/java/org/apache/ignite/configuration/IgniteConfiguration.java
@@ -60,7 +60,7 @@ import static org.apache.ignite.plugin.segmentation.GridSegmentationPolicy.*;
  * {@link org.apache.ignite.Ignition#start(IgniteConfiguration)} method. It defines all configuration
  * parameters required to start a grid instance. Usually, a special
  * class called "loader" will create an instance of this interface and apply
- * {@link org.apache.ignite.Ignition#start(IgniteConfiguration)} method to initialize GridGain instance.
+ * {@link org.apache.ignite.Ignition#start(IgniteConfiguration)} method to initialize Ignite instance.
  * <p>
  * Note that you should only set values that differ from defaults, as grid
  * will automatically pick default values for all values that are not set.
@@ -677,7 +677,7 @@ public class IgniteConfiguration {
     /**
      * Whether or not to use SSL fot SMTP. Default is {@link #DFLT_SMTP_SSL}.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -696,7 +696,7 @@ public class IgniteConfiguration {
     /**
      * Whether or not to use STARTTLS fot SMTP. Default is {@link #DFLT_SMTP_STARTTLS}.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -715,7 +715,7 @@ public class IgniteConfiguration {
     /**
      * Gets SMTP host name or {@code null} if SMTP is not configured.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -733,7 +733,7 @@ public class IgniteConfiguration {
     /**
      * Gets SMTP port. Default value is {@link #DFLT_SMTP_PORT}.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -752,7 +752,7 @@ public class IgniteConfiguration {
     /**
      * Gets SMTP username or {@code null} if not used.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -770,7 +770,7 @@ public class IgniteConfiguration {
     /**
      * SMTP password or {@code null} if not used.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -788,7 +788,7 @@ public class IgniteConfiguration {
     /**
      * Gets optional set of admin emails where email notifications will be set.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -837,7 +837,7 @@ public class IgniteConfiguration {
     /**
      * Sets whether or not SMTP uses SSL.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -855,7 +855,7 @@ public class IgniteConfiguration {
     /**
      * Sets whether or not SMTP uses STARTTLS.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -873,7 +873,7 @@ public class IgniteConfiguration {
     /**
      * Sets SMTP host.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -891,7 +891,7 @@ public class IgniteConfiguration {
     /**
      * Sets SMTP port. Default value is {@link #DFLT_SMTP_PORT}.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -910,7 +910,7 @@ public class IgniteConfiguration {
     /**
      * Sets SMTP username or {@code null} if not used.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -928,7 +928,7 @@ public class IgniteConfiguration {
     /**
      * Sets SMTP password or {@code null} if not used.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -946,7 +946,7 @@ public class IgniteConfiguration {
     /**
      * Sets optional set of admin emails where email notifications will be set.
      * <p>
-     * Note that GridGain uses SMTP to send emails in critical
+     * Note that Ignite uses SMTP to send emails in critical
      * situations such as license expiration or fatal system errors.
      * It is <b>highly</b> recommended to configure SMTP in production
      * environment.
@@ -992,7 +992,7 @@ public class IgniteConfiguration {
      * way to see daemon nodes is to use {@link org.apache.ignite.cluster.ClusterGroup#forDaemons()} method.
      * <p>
      * Daemon nodes are used primarily for management and monitoring functionality that
-     * is build on GridGain and needs to participate in the topology but also needs to be
+     * is build on Ignite and needs to participate in the topology but also needs to be
      * excluded from "normal" topology so that it won't participate in task execution
      * or in-memory data grid storage.
      *
@@ -1011,7 +1011,7 @@ public class IgniteConfiguration {
      * way to see daemon nodes is to use {@link org.apache.ignite.cluster.ClusterGroup#forDaemons()} method.
      * <p>
      * Daemon nodes are used primarily for management and monitoring functionality that
-     * is build on GridGain and needs to participate in the topology but also needs to be
+     * is build on Ignite and needs to participate in the topology but also needs to be
      * excluded from "normal" topology so that it won't participate in task execution
      * or in-memory data grid storage.
      *
@@ -1180,8 +1180,8 @@ public class IgniteConfiguration {
      * Shutdown flag for executor service.
      * <p>
      * If not provided, default value {@code true} will be used which will shutdown
-     * executor service when GridGain stops regardless of whether it was started before
-     * GridGain or by GridGain.
+     * executor service when Ignite stops regardless of whether it was started before
+     * Ignite or by Ignition.
      *
      * @return Executor service shutdown flag.
      */
@@ -1193,8 +1193,8 @@ public class IgniteConfiguration {
      * Shutdown flag for system executor service.
      * <p>
      * If not provided, default value {@code true} will be used which will shutdown
-     * executor service when GridGain stops regardless of whether it was started before
-     * GridGain or by GridGain.
+     * executor service when Ignite stops regardless of whether it was started before
+     * Ignite or by Ignition.
      *
      * @return System executor service shutdown flag.
      */
@@ -1206,8 +1206,8 @@ public class IgniteConfiguration {
      * Shutdown flag for management executor service.
      * <p>
      * If not provided, default value {@code true} will be used which will shutdown
-     * executor service when GridGain stops regardless of whether it was started before
-     * GridGain or by GridGain.
+     * executor service when Ignite stops regardless of whether it was started before
+     * Ignite or by Ignition.
      *
      * @return Management executor service shutdown flag.
      */
@@ -1231,8 +1231,8 @@ public class IgniteConfiguration {
      * Shutdown flag for GGFS executor service.
      * <p>
      * If not provided, default value {@code true} will be used which will shutdown
-     * executor service when GridGain stops regardless whether it was started before GridGain
-     * or by GridGain.
+     * executor service when Ignite stops regardless whether it was started before Ignition
+     * or by Ignition.
      *
      * @return GGFS executor service shutdown flag.
      */
@@ -1341,12 +1341,12 @@ public class IgniteConfiguration {
     }
 
     /**
-     * Should return GridGain installation home folder. If not provided, the system will check
+     * Should return Ignite installation home folder. If not provided, the system will check
      * {@code IGNITE_HOME} system property and environment variable in that order. If
      * {@code IGNITE_HOME} still could not be obtained, then grid will not start and exception
      * will be thrown.
      *
-     * @return GridGain installation home or {@code null} to make the system attempt to
+     * @return Ignite installation home or {@code null} to make the system attempt to
      *      infer it automatically.
      * @see org.apache.ignite.IgniteSystemProperties#IGNITE_HOME
      */
@@ -1355,9 +1355,9 @@ public class IgniteConfiguration {
     }
 
     /**
-     * Sets GridGain installation folder.
+     * Sets Ignite installation folder.
      *
-     * @param ggHome {@code GridGain} installation folder.
+     * @param ggHome {@code Ignition} installation folder.
      * @see IgniteConfiguration#getGridGainHome()
      * @see org.apache.ignite.IgniteSystemProperties#IGNITE_HOME
      */
@@ -1366,13 +1366,13 @@ public class IgniteConfiguration {
     }
 
     /**
-     * Gets GridGain work folder. If not provided, the method will use work folder under
+     * Gets Ignite work folder. If not provided, the method will use work folder under
      * {@code IGNITE_HOME} specified by {@link IgniteConfiguration#setGridGainHome(String)} or
      * {@code IGNITE_HOME} environment variable or system property.
      * <p>
      * If {@code IGNITE_HOME} is not provided, then system temp folder is used.
      *
-     * @return GridGain work folder or {@code null} to make the system attempt to infer it automatically.
+     * @return Ignite work folder or {@code null} to make the system attempt to infer it automatically.
      * @see IgniteConfiguration#getGridGainHome()
      * @see org.apache.ignite.IgniteSystemProperties#IGNITE_HOME
      */
@@ -1381,9 +1381,9 @@ public class IgniteConfiguration {
     }
 
     /**
-     * Sets GridGain work folder.
+     * Sets Ignite work folder.
      *
-     * @param ggWork {@code GridGain} work folder.
+     * @param ggWork {@code Ignite} work folder.
      * @see IgniteConfiguration#getWorkDirectory()
      */
     public void setWorkDirectory(String ggWork) {
@@ -2249,7 +2249,7 @@ public class IgniteConfiguration {
     }
 
     /**
-     * Gets flag indicating whether cache sanity check is enabled. If enabled, then GridGain
+     * Gets flag indicating whether cache sanity check is enabled. If enabled, then Ignite
      * will perform the following checks and throw an exception if check fails:
      * <ul>
      *     <li>Cache entry is not externally locked with {@code lock(...)} or {@code lockAsync(...)}
@@ -2284,13 +2284,13 @@ public class IgniteConfiguration {
     /**
      * Gets array of event types, which will be recorded.
      * <p>
-     * Note that by default all events in GridGain are disabled. GridGain can and often does generate thousands
+     * Note that by default all events in Ignite are disabled. Ignite can and often does generate thousands
      * events per seconds under the load and therefore it creates a significant additional load on the system.
      * If these events are not needed by the application this load is unnecessary and leads to significant
      * performance degradation. So it is <b>highly recommended</b> to enable only those events that your
-     * application logic requires. Note that certain events are required for GridGain's internal operations
+     * application logic requires. Note that certain events are required for Ignite's internal operations
      * and such events will still be generated but not stored by event storage SPI if they are disabled
-     * in GridGain configuration.
+     * in Ignite configuration.
      *
      * @return Include event types.
      */
@@ -2311,7 +2311,7 @@ public class IgniteConfiguration {
     /**
      * Sets path, either absolute or relative to {@code IGNITE_HOME}, to {@code JETTY}
      * XML configuration file. {@code JETTY} is used to support REST over HTTP protocol for
-     * accessing GridGain APIs remotely.
+     * accessing Ignite APIs remotely.
      *
      * @param jettyPath Path to {@code JETTY} XML configuration file.
      * @deprecated Use {@link ClientConnectionConfiguration#setRestJettyPath(String)}.
@@ -2324,7 +2324,7 @@ public class IgniteConfiguration {
     /**
      * Gets path, either absolute or relative to {@code IGNITE_HOME}, to {@code Jetty}
      * XML configuration file. {@code Jetty} is used to support REST over HTTP protocol for
-     * accessing GridGain APIs remotely.
+     * accessing Ignite APIs remotely.
      * <p>
      * If not provided, Jetty instance with default configuration will be started picking
      * {@link org.apache.ignite.IgniteSystemProperties#IGNITE_JETTY_HOST} and {@link org.apache.ignite.IgniteSystemProperties#IGNITE_JETTY_PORT}
@@ -2765,8 +2765,8 @@ public class IgniteConfiguration {
      * Shutdown flag for REST executor service.
      * <p>
      * If not provided, default value {@code true} will be used which will shutdown
-     * executor service when GridGain stops regardless whether it was started before GridGain
-     * or by GridGain.
+     * executor service when Ignite stops regardless whether it was started before Ignite
+     * or by Ignite.
      *
      * @return REST executor service shutdown flag.
      * @deprecated Use {@link ClientConnectionConfiguration#isRestExecutorServiceShutdown()}.
@@ -2777,8 +2777,8 @@ public class IgniteConfiguration {
     }
 
     /**
-     * Sets system-wide local address or host for all GridGain components to bind to. If provided it will
-     * override all default local bind settings within GridGain or any of its SPIs.
+     * Sets system-wide local address or host for all Ignite components to bind to. If provided it will
+     * override all default local bind settings within Ignite or any of its SPIs.
      *
      * @param locHost Local IP address or host to bind to.
      */
@@ -2787,10 +2787,10 @@ public class IgniteConfiguration {
     }
 
     /**
-     * Gets system-wide local address or host for all GridGain components to bind to. If provided it will
-     * override all default local bind settings within GridGain or any of its SPIs.
+     * Gets system-wide local address or host for all Ignite components to bind to. If provided it will
+     * override all default local bind settings within Ignite or any of its SPIs.
      * <p>
-     * If {@code null} then GridGain tries to use local wildcard address. That means that
+     * If {@code null} then Ignite tries to use local wildcard address. That means that
      * all services will be available on all network interfaces of the host machine.
      * <p>
      * It is strongly recommended to set this parameter for all production environments.

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/configuration/IgniteDeploymentMode.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/configuration/IgniteDeploymentMode.java b/modules/core/src/main/java/org/apache/ignite/configuration/IgniteDeploymentMode.java
index ba410bc..774a5a4 100644
--- a/modules/core/src/main/java/org/apache/ignite/configuration/IgniteDeploymentMode.java
+++ b/modules/core/src/main/java/org/apache/ignite/configuration/IgniteDeploymentMode.java
@@ -34,7 +34,7 @@ import org.jetbrains.annotations.*;
  * </ul>
  * <h1 class="header">User Version</h1>
  * User version comes into play whenever you would like to redeploy tasks deployed
- * in {@link #SHARED} or {@link #CONTINUOUS} modes. By default, GridGain will
+ * in {@link #SHARED} or {@link #CONTINUOUS} modes. By default, Ignite will
  * automatically detect if class-loader changed or a node is restarted. However,
  * if you would like to change and redeploy code on a subset of nodes, or in
  * case of {@link #CONTINUOUS} mode to kill the ever living deployment, you should
@@ -54,13 +54,13 @@ import org.jetbrains.annotations.*;
  * file with desired user version in it.
  * <p>
  * <h1 class="header">Always-Local Development</h1>
- * GridGain deployment (regardless of mode) allows you to develop everything as you would
+ * Ignite deployment (regardless of mode) allows you to develop everything as you would
  * locally. You never need to specifically write any kind of code for remote nodes. For
  * example, if you need to use a distributed cache from your {@link org.apache.ignite.compute.ComputeJob}, then you can
  * the following:
  * <ol>
  *  <li>
- *      Simply startup stand-alone GridGain nodes by executing
+ *      Simply startup stand-alone Ignite nodes by executing
  *      {@code IGNITE_HOME/ignite.{sh|bat}} scripts.
  *  </li>
  *  <li>
@@ -120,7 +120,7 @@ public enum IgniteDeploymentMode {
      * different master nodes share the same instances of resources on worker nodes. This allows for all
      * tasks executing on remote nodes to reuse, for example, the same instances of
      * connection pools or caches. When using this mode, you can
-     * startup multiple stand-alone GridGain worker nodes, define resources
+     * startup multiple stand-alone Ignite worker nodes, define resources
      * on master nodes and have them initialize once on worker nodes regardless
      * of which master node they came from.
      * <p>
@@ -149,7 +149,7 @@ public enum IgniteDeploymentMode {
      * different master nodes share the same instances of resources on worker nodes. This allows for all
      * tasks executing on remote nodes to reuse, for example, the same instances of
      * connection pools or caches. When using this mode, you can
-     * startup multiple stand-alone GridGain worker nodes, define resources
+     * startup multiple stand-alone Ignite worker nodes, define resources
      * on master nodes and have them initialize once on worker nodes regardless
      * of which master node they came from.
      * <p>

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/configuration/IgniteQueryConfiguration.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/configuration/IgniteQueryConfiguration.java b/modules/core/src/main/java/org/apache/ignite/configuration/IgniteQueryConfiguration.java
index d4a5e2f..d6577ba 100644
--- a/modules/core/src/main/java/org/apache/ignite/configuration/IgniteQueryConfiguration.java
+++ b/modules/core/src/main/java/org/apache/ignite/configuration/IgniteQueryConfiguration.java
@@ -56,7 +56,7 @@ public class IgniteQueryConfiguration {
      * <ul>
      * <li>{@code -1} - Means that off-heap storage is disabled.</li>
      * <li>
-     *     {@code 0} - GridGain will not limit off-heap storage (it's up to user to properly
+     *     {@code 0} - Ignite will not limit off-heap storage (it's up to user to properly
      *     add and remove entries from cache to ensure that off-heap storage does not grow
      *     indefinitely.
      * </li>
@@ -66,7 +66,7 @@ public class IgniteQueryConfiguration {
      * <p>
      * Use off-heap storage to load gigabytes of data in memory without slowing down
      * Garbage Collection. Essentially in this case you should allocate very small amount
-     * of memory to JVM and GridGain will cache most of the data in off-heap space
+     * of memory to JVM and Ignite will cache most of the data in off-heap space
      * without affecting JVM performance at all.
      *
      * @param maxOffHeapMemory Maximum memory in bytes available to off-heap memory space.
@@ -176,7 +176,7 @@ public class IgniteQueryConfiguration {
     }
 
     /**
-     * The flag indicating that serializer for H2 database will be set to GridGain's marshaller.
+     * The flag indicating that serializer for H2 database will be set to Ignite's marshaller.
      * This setting usually makes sense for offheap indexing only.
      * <p>
      * Default is {@link #DFLT_USE_OPTIMIZED_SERIALIZER}.
@@ -188,7 +188,7 @@ public class IgniteQueryConfiguration {
     }
 
     /**
-     * The flag indicating that serializer for H2 database will be set to GridGain's marshaller.
+     * The flag indicating that serializer for H2 database will be set to Ignite's marshaller.
      * This setting usually makes sense for offheap indexing only.
      * <p>
      * Default is {@link #DFLT_USE_OPTIMIZED_SERIALIZER}.

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/events/IgniteAuthenticationEvent.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/events/IgniteAuthenticationEvent.java b/modules/core/src/main/java/org/apache/ignite/events/IgniteAuthenticationEvent.java
index 71a424e..84eb508 100644
--- a/modules/core/src/main/java/org/apache/ignite/events/IgniteAuthenticationEvent.java
+++ b/modules/core/src/main/java/org/apache/ignite/events/IgniteAuthenticationEvent.java
@@ -28,7 +28,7 @@ import java.util.*;
  * Grid authentication event.
  * <p>
  * Grid events are used for notification about what happens within the grid. Note that by
- * design GridGain keeps all events generated on the local node locally and it provides
+ * design Ignite keeps all events generated on the local node locally and it provides
  * APIs for performing a distributed queries across multiple nodes:
  * <ul>
  *      <li>
@@ -47,9 +47,9 @@ import java.util.*;
  * User can also wait for events using method {@link org.apache.ignite.IgniteEvents#waitForLocal(org.apache.ignite.lang.IgnitePredicate, int...)}.
  * <h1 class="header">Events and Performance</h1>
  * It is <b>highly recommended</b> to enable only those events that your application logic requires
- * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in GridGain configuration. Note that certain
- * events are required for GridGain's internal operations and such events will still be generated but not stored by
- * event storage SPI if they are disabled in GridGain configuration.
+ * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in Ignite configuration. Note that certain
+ * events are required for Ignite's internal operations and such events will still be generated but not stored by
+ * event storage SPI if they are disabled in Ignite configuration.
  * @see IgniteEventType#EVT_AUTHENTICATION_FAILED
  * @see IgniteEventType#EVT_AUTHENTICATION_SUCCEEDED
  */

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/events/IgniteAuthorizationEvent.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/events/IgniteAuthorizationEvent.java b/modules/core/src/main/java/org/apache/ignite/events/IgniteAuthorizationEvent.java
index fb2d5e2..9b23c1a 100644
--- a/modules/core/src/main/java/org/apache/ignite/events/IgniteAuthorizationEvent.java
+++ b/modules/core/src/main/java/org/apache/ignite/events/IgniteAuthorizationEvent.java
@@ -25,7 +25,7 @@ import org.apache.ignite.plugin.security.*;
  * Grid authorization event.
  * <p>
  * Grid events are used for notification about what happens within the grid. Note that by
- * design GridGain keeps all events generated on the local node locally and it provides
+ * design Ignite keeps all events generated on the local node locally and it provides
  * APIs for performing a distributed queries across multiple nodes:
  * <ul>
  *      <li>
@@ -44,9 +44,9 @@ import org.apache.ignite.plugin.security.*;
  * User can also wait for events using method {@link org.apache.ignite.IgniteEvents#waitForLocal(org.apache.ignite.lang.IgnitePredicate, int...)}.
  * <h1 class="header">Events and Performance</h1>
  * It is <b>highly recommended</b> to enable only those events that your application logic requires
- * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in GridGain configuration. Note that certain
- * events are required for GridGain's internal operations and such events will still be generated but not stored by
- * event storage SPI if they are disabled in GridGain configuration.
+ * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in Ignite configuration. Note that certain
+ * events are required for Ignite's internal operations and such events will still be generated but not stored by
+ * event storage SPI if they are disabled in Ignite configuration.
  * @see IgniteEventType#EVT_AUTHORIZATION_FAILED
  * @see IgniteEventType#EVT_AUTHORIZATION_SUCCEEDED
  */

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheEvent.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheEvent.java b/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheEvent.java
index 9c944c9..7cf35a4 100644
--- a/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheEvent.java
+++ b/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheEvent.java
@@ -29,7 +29,7 @@ import java.util.*;
  * In-memory database (cache) event.
  * <p>
  * Grid events are used for notification about what happens within the grid. Note that by
- * design GridGain keeps all events generated on the local node locally and it provides
+ * design Ignite keeps all events generated on the local node locally and it provides
  * APIs for performing a distributed queries across multiple nodes:
  * <ul>
  *      <li>
@@ -47,15 +47,15 @@ import java.util.*;
  * </ul>
  * User can also wait for events using method {@link org.apache.ignite.IgniteEvents#waitForLocal(org.apache.ignite.lang.IgnitePredicate, int...)}.
  * <h1 class="header">Events and Performance</h1>
- * Note that by default all events in GridGain are enabled and therefore generated and stored
- * by whatever event storage SPI is configured. GridGain can and often does generate thousands events per seconds
+ * Note that by default all events in Ignite are enabled and therefore generated and stored
+ * by whatever event storage SPI is configured. Ignite can and often does generate thousands events per seconds
  * under the load and therefore it creates a significant additional load on the system. If these events are
  * not needed by the application this load is unnecessary and leads to significant performance degradation.
  * <p>
  * It is <b>highly recommended</b> to enable only those events that your application logic requires
- * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in GridGain configuration. Note that certain
- * events are required for GridGain's internal operations and such events will still be generated but not stored by
- * event storage SPI if they are disabled in GridGain configuration.
+ * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in Ignite configuration. Note that certain
+ * events are required for Ignite's internal operations and such events will still be generated but not stored by
+ * event storage SPI if they are disabled in Ignite configuration.
  * @see IgniteEventType#EVT_CACHE_ENTRY_CREATED
  * @see IgniteEventType#EVT_CACHE_ENTRY_DESTROYED
  * @see IgniteEventType#EVT_CACHE_ENTRY_EVICTED

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/events/IgniteCachePreloadingEvent.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/events/IgniteCachePreloadingEvent.java b/modules/core/src/main/java/org/apache/ignite/events/IgniteCachePreloadingEvent.java
index 5a699cf..68c42a2 100644
--- a/modules/core/src/main/java/org/apache/ignite/events/IgniteCachePreloadingEvent.java
+++ b/modules/core/src/main/java/org/apache/ignite/events/IgniteCachePreloadingEvent.java
@@ -25,7 +25,7 @@ import org.apache.ignite.internal.util.typedef.internal.*;
  * in grid topology, which means that a node has either joined or left the grid.
  * <p>
  * Grid events are used for notification about what happens within the grid. Note that by
- * design GridGain keeps all events generated on the local node locally and it provides
+ * design Ignite keeps all events generated on the local node locally and it provides
  * APIs for performing a distributed queries across multiple nodes:
  * <ul>
  *      <li>
@@ -43,15 +43,15 @@ import org.apache.ignite.internal.util.typedef.internal.*;
  * </ul>
  * User can also wait for events using method {@link org.apache.ignite.IgniteEvents#waitForLocal(org.apache.ignite.lang.IgnitePredicate, int...)}.
  * <h1 class="header">Events and Performance</h1>
- * Note that by default all events in GridGain are enabled and therefore generated and stored
- * by whatever event storage SPI is configured. GridGain can and often does generate thousands events per seconds
+ * Note that by default all events in Ignite are enabled and therefore generated and stored
+ * by whatever event storage SPI is configured. Ignite can and often does generate thousands events per seconds
  * under the load and therefore it creates a significant additional load on the system. If these events are
  * not needed by the application this load is unnecessary and leads to significant performance degradation.
  * <p>
  * It is <b>highly recommended</b> to enable only those events that your application logic requires
- * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in GridGain configuration. Note that certain
- * events are required for GridGain's internal operations and such events will still be generated but not stored by
- * event storage SPI if they are disabled in GridGain configuration.
+ * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in Ignite configuration. Note that certain
+ * events are required for Ignite's internal operations and such events will still be generated but not stored by
+ * event storage SPI if they are disabled in Ignite configuration.
  * @see IgniteEventType#EVT_CACHE_PRELOAD_PART_LOADED
  * @see IgniteEventType#EVT_CACHE_PRELOAD_PART_UNLOADED
  * @see IgniteEventType#EVT_CACHE_PRELOAD_STARTED

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheQueryExecutedEvent.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheQueryExecutedEvent.java b/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheQueryExecutedEvent.java
index 18631d3..9f9c08a 100644
--- a/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheQueryExecutedEvent.java
+++ b/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheQueryExecutedEvent.java
@@ -30,7 +30,7 @@ import java.util.*;
  * Cache query execution event.
  * <p>
  * Grid events are used for notification about what happens within the grid. Note that by
- * design GridGain keeps all events generated on the local node locally and it provides
+ * design Ignite keeps all events generated on the local node locally and it provides
  * APIs for performing a distributed queries across multiple nodes:
  * <ul>
  *      <li>
@@ -48,15 +48,15 @@ import java.util.*;
  * </ul>
  * User can also wait for events using method {@link org.apache.ignite.IgniteEvents#waitForLocal(org.apache.ignite.lang.IgnitePredicate, int...)}.
  * <h1 class="header">Events and Performance</h1>
- * Note that by default all events in GridGain are enabled and therefore generated and stored
- * by whatever event storage SPI is configured. GridGain can and often does generate thousands events per seconds
+ * Note that by default all events in Ignite are enabled and therefore generated and stored
+ * by whatever event storage SPI is configured. Ignite can and often does generate thousands events per seconds
  * under the load and therefore it creates a significant additional load on the system. If these events are
  * not needed by the application this load is unnecessary and leads to significant performance degradation.
  * <p>
  * It is <b>highly recommended</b> to enable only those events that your application logic requires
- * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in GridGain configuration. Note that certain
- * events are required for GridGain's internal operations and such events will still be generated but not stored by
- * event storage SPI if they are disabled in GridGain configuration.
+ * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in Ignite configuration. Note that certain
+ * events are required for Ignite's internal operations and such events will still be generated but not stored by
+ * event storage SPI if they are disabled in Ignite configuration.
  *
  * @see IgniteEventType#EVT_CACHE_QUERY_EXECUTED
  * @see IgniteEventType#EVTS_CACHE_QUERY

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheQueryReadEvent.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheQueryReadEvent.java b/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheQueryReadEvent.java
index 9d0dcf6..6b59542 100644
--- a/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheQueryReadEvent.java
+++ b/modules/core/src/main/java/org/apache/ignite/events/IgniteCacheQueryReadEvent.java
@@ -30,7 +30,7 @@ import java.util.*;
  * Cache query read event.
  * <p>
  * Grid events are used for notification about what happens within the grid. Note that by
- * design GridGain keeps all events generated on the local node locally and it provides
+ * design Ignite keeps all events generated on the local node locally and it provides
  * APIs for performing a distributed queries across multiple nodes:
  * <ul>
  *      <li>
@@ -48,15 +48,15 @@ import java.util.*;
  * </ul>
  * User can also wait for events using method {@link org.apache.ignite.IgniteEvents#waitForLocal(org.apache.ignite.lang.IgnitePredicate, int...)}.
  * <h1 class="header">Events and Performance</h1>
- * Note that by default all events in GridGain are enabled and therefore generated and stored
- * by whatever event storage SPI is configured. GridGain can and often does generate thousands events per seconds
+ * Note that by default all events in Ignite are enabled and therefore generated and stored
+ * by whatever event storage SPI is configured. Ignite can and often does generate thousands events per seconds
  * under the load and therefore it creates a significant additional load on the system. If these events are
  * not needed by the application this load is unnecessary and leads to significant performance degradation.
  * <p>
  * It is <b>highly recommended</b> to enable only those events that your application logic requires
- * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in GridGain configuration. Note that certain
- * events are required for GridGain's internal operations and such events will still be generated but not stored by
- * event storage SPI if they are disabled in GridGain configuration.
+ * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in Ignite configuration. Note that certain
+ * events are required for Ignite's internal operations and such events will still be generated but not stored by
+ * event storage SPI if they are disabled in Ignite configuration.
  *
  * @see IgniteEventType#EVT_CACHE_QUERY_OBJECT_READ
  * @see IgniteEventType#EVTS_CACHE_QUERY

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/events/IgniteCheckpointEvent.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/events/IgniteCheckpointEvent.java b/modules/core/src/main/java/org/apache/ignite/events/IgniteCheckpointEvent.java
index 1f25555..e7f0434 100644
--- a/modules/core/src/main/java/org/apache/ignite/events/IgniteCheckpointEvent.java
+++ b/modules/core/src/main/java/org/apache/ignite/events/IgniteCheckpointEvent.java
@@ -24,7 +24,7 @@ import org.apache.ignite.internal.util.typedef.internal.*;
  * Grid checkpoint event.
  * <p>
  * Grid events are used for notification about what happens within the grid. Note that by
- * design GridGain keeps all events generated on the local node locally and it provides
+ * design Ignite keeps all events generated on the local node locally and it provides
  * APIs for performing a distributed queries across multiple nodes:
  * <ul>
  *      <li>
@@ -42,15 +42,15 @@ import org.apache.ignite.internal.util.typedef.internal.*;
  * </ul>
  * User can also wait for events using method {@link org.apache.ignite.IgniteEvents#waitForLocal(org.apache.ignite.lang.IgnitePredicate, int...)}.
  * <h1 class="header">Events and Performance</h1>
- * Note that by default all events in GridGain are enabled and therefore generated and stored
- * by whatever event storage SPI is configured. GridGain can and often does generate thousands events per seconds
+ * Note that by default all events in Ignite are enabled and therefore generated and stored
+ * by whatever event storage SPI is configured. Ignite can and often does generate thousands events per seconds
  * under the load and therefore it creates a significant additional load on the system. If these events are
  * not needed by the application this load is unnecessary and leads to significant performance degradation.
  * <p>
  * It is <b>highly recommended</b> to enable only those events that your application logic requires
- * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in GridGain configuration. Note that certain
- * events are required for GridGain's internal operations and such events will still be generated but not stored by
- * event storage SPI if they are disabled in GridGain configuration.
+ * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in Ignite configuration. Note that certain
+ * events are required for Ignite's internal operations and such events will still be generated but not stored by
+ * event storage SPI if they are disabled in Ignite configuration.
  * @see IgniteEventType#EVT_CHECKPOINT_LOADED
  * @see IgniteEventType#EVT_CHECKPOINT_REMOVED
  * @see IgniteEventType#EVT_CHECKPOINT_SAVED

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/events/IgniteDeploymentEvent.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/events/IgniteDeploymentEvent.java b/modules/core/src/main/java/org/apache/ignite/events/IgniteDeploymentEvent.java
index 2e62647..5c34044 100644
--- a/modules/core/src/main/java/org/apache/ignite/events/IgniteDeploymentEvent.java
+++ b/modules/core/src/main/java/org/apache/ignite/events/IgniteDeploymentEvent.java
@@ -24,7 +24,7 @@ import org.apache.ignite.internal.util.typedef.internal.*;
  * Grid deployment event.
  * <p>
  * Grid events are used for notification about what happens within the grid. Note that by
- * design GridGain keeps all events generated on the local node locally and it provides
+ * design Ignite keeps all events generated on the local node locally and it provides
  * APIs for performing a distributed queries across multiple nodes:
  * <ul>
  *      <li>
@@ -42,15 +42,15 @@ import org.apache.ignite.internal.util.typedef.internal.*;
  * </ul>
  * User can also wait for events using method {@link org.apache.ignite.IgniteEvents#waitForLocal(org.apache.ignite.lang.IgnitePredicate, int...)}.
  * <h1 class="header">Events and Performance</h1>
- * Note that by default all events in GridGain are enabled and therefore generated and stored
- * by whatever event storage SPI is configured. GridGain can and often does generate thousands events per seconds
+ * Note that by default all events in Ignite are enabled and therefore generated and stored
+ * by whatever event storage SPI is configured. Ignite can and often does generate thousands events per seconds
  * under the load and therefore it creates a significant additional load on the system. If these events are
  * not needed by the application this load is unnecessary and leads to significant performance degradation.
  * <p>
  * It is <b>highly recommended</b> to enable only those events that your application logic requires
- * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in GridGain configuration. Note that certain
- * events are required for GridGain's internal operations and such events will still be generated but not stored by
- * event storage SPI if they are disabled in GridGain configuration.
+ * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in Ignite configuration. Note that certain
+ * events are required for Ignite's internal operations and such events will still be generated but not stored by
+ * event storage SPI if they are disabled in Ignite configuration.
  * @see IgniteEventType#EVT_CLASS_DEPLOY_FAILED
  * @see IgniteEventType#EVT_CLASS_DEPLOYED
  * @see IgniteEventType#EVT_CLASS_UNDEPLOYED

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/events/IgniteDiscoveryEvent.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/events/IgniteDiscoveryEvent.java b/modules/core/src/main/java/org/apache/ignite/events/IgniteDiscoveryEvent.java
index 87249bd..2549079 100644
--- a/modules/core/src/main/java/org/apache/ignite/events/IgniteDiscoveryEvent.java
+++ b/modules/core/src/main/java/org/apache/ignite/events/IgniteDiscoveryEvent.java
@@ -27,7 +27,7 @@ import java.util.*;
  * Grid discovery event.
  * <p>
  * Grid events are used for notification about what happens within the grid. Note that by
- * design GridGain keeps all events generated on the local node locally and it provides
+ * design Ignite keeps all events generated on the local node locally and it provides
  * APIs for performing a distributed queries across multiple nodes:
  * <ul>
  *      <li>
@@ -45,15 +45,15 @@ import java.util.*;
  * </ul>
  * User can also wait for events using method {@link org.apache.ignite.IgniteEvents#waitForLocal(org.apache.ignite.lang.IgnitePredicate, int...)}.
  * <h1 class="header">Events and Performance</h1>
- * Note that by default all events in GridGain are enabled and therefore generated and stored
- * by whatever event storage SPI is configured. GridGain can and often does generate thousands events per seconds
+ * Note that by default all events in Ignite are enabled and therefore generated and stored
+ * by whatever event storage SPI is configured. Ignite can and often does generate thousands events per seconds
  * under the load and therefore it creates a significant additional load on the system. If these events are
  * not needed by the application this load is unnecessary and leads to significant performance degradation.
  * <p>
  * It is <b>highly recommended</b> to enable only those events that your application logic requires
- * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in GridGain configuration. Note that certain
- * events are required for GridGain's internal operations and such events will still be generated but not stored by
- * event storage SPI if they are disabled in GridGain configuration.
+ * by using {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in Ignite configuration. Note that certain
+ * events are required for Ignite's internal operations and such events will still be generated but not stored by
+ * event storage SPI if they are disabled in Ignite configuration.
  * @see IgniteEventType#EVT_NODE_METRICS_UPDATED
  * @see IgniteEventType#EVT_NODE_FAILED
  * @see IgniteEventType#EVT_NODE_JOINED

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/86ab8e20/modules/core/src/main/java/org/apache/ignite/events/IgniteEvent.java
----------------------------------------------------------------------
diff --git a/modules/core/src/main/java/org/apache/ignite/events/IgniteEvent.java b/modules/core/src/main/java/org/apache/ignite/events/IgniteEvent.java
index 2eaf479..69d5064 100644
--- a/modules/core/src/main/java/org/apache/ignite/events/IgniteEvent.java
+++ b/modules/core/src/main/java/org/apache/ignite/events/IgniteEvent.java
@@ -25,7 +25,7 @@ import java.io.*;
 
 /**
  * Grid events are used for notification about what happens within the grid. Note that by
- * design GridGain keeps all events generated on the local node locally and it provides
+ * design Ignite keeps all events generated on the local node locally and it provides
  * APIs for performing a distributed queries across multiple nodes:
  * <ul>
  *      <li>
@@ -42,15 +42,15 @@ import java.io.*;
  *      </li>
  * </ul>
  * <h1 class="header">Events and Performance</h1>
- * Note that by default all events in GridGain are enabled and therefore generated and stored
- * by whatever event storage SPI is configured. GridGain can and often does generate thousands events per seconds
+ * Note that by default all events in Ignite are enabled and therefore generated and stored
+ * by whatever event storage SPI is configured. Ignite can and often does generate thousands events per seconds
  * under the load and therefore it creates a significant additional load on the system. If these events are
  * not needed by the application this load is unnecessary and leads to significant performance degradation.
  * <p>
  * It is <b>highly recommended</b> to enable only those events that your application logic requires
- * by using either {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in GridGain configuration. Note that certain
- * events are required for GridGain's internal operations and such events will still be generated but not stored by
- * event storage SPI if they are disabled in GridGain configuration.
+ * by using either {@link org.apache.ignite.configuration.IgniteConfiguration#getIncludeEventTypes()} method in Ignite configuration. Note that certain
+ * events are required for Ignite's internal operations and such events will still be generated but not stored by
+ * event storage SPI if they are disabled in Ignite configuration.
  * <h1 class="header">Internal and Hidden Events</h1>
  * Also note that some events are considered to be internally used or hidden.
  * <p>
@@ -96,7 +96,7 @@ public interface IgniteEvent extends Comparable<IgniteEvent>, Serializable {
      * Gets locally unique ID that is atomically incremented for each event. Unlike
      * global {@link #id} this local ID can be used for ordering events on this node.
      * <p>
-     * Note that for performance considerations GridGain doesn't order events globally.
+     * Note that for performance considerations Ignite doesn't order events globally.
      *
      * @return Locally unique ID that is atomically incremented for each new event.
      * @see #id()
@@ -122,7 +122,7 @@ public interface IgniteEvent extends Comparable<IgniteEvent>, Serializable {
      * {@link IgniteEventType}.
      * <p>
      * NOTE: all types in range <b>from 1 to 1000 are reserved</b> for
-     * internal GridGain events and should not be used by user-defined events.
+     * internal Ignite events and should not be used by user-defined events.
      *
      * @return Event's type.
      * @see IgniteEventType


Mime
View raw message