helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ka...@apache.org
Subject git commit: [HELIX-383] Fix Javadoc for HelixManager usage
Date Thu, 20 Feb 2014 22:29:34 GMT
Repository: helix
Updated Branches:
  refs/heads/helix-0.6.2-release 5b73a826b -> 44707c6c6


[HELIX-383] Fix Javadoc for HelixManager usage


Project: http://git-wip-us.apache.org/repos/asf/helix/repo
Commit: http://git-wip-us.apache.org/repos/asf/helix/commit/44707c6c
Tree: http://git-wip-us.apache.org/repos/asf/helix/tree/44707c6c
Diff: http://git-wip-us.apache.org/repos/asf/helix/diff/44707c6c

Branch: refs/heads/helix-0.6.2-release
Commit: 44707c6c6b0a58da1c54aa0fdf341fae2f030a39
Parents: 5b73a82
Author: Kanak Biscuitwala <kanak@apache.org>
Authored: Thu Feb 20 14:03:20 2014 -0800
Committer: Kanak Biscuitwala <kanak@apache.org>
Committed: Thu Feb 20 14:29:23 2014 -0800

----------------------------------------------------------------------
 helix-core/src/main/java/org/apache/helix/HelixManager.java | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/helix/blob/44707c6c/helix-core/src/main/java/org/apache/helix/HelixManager.java
----------------------------------------------------------------------
diff --git a/helix-core/src/main/java/org/apache/helix/HelixManager.java b/helix-core/src/main/java/org/apache/helix/HelixManager.java
index a400686..620db05 100644
--- a/helix-core/src/main/java/org/apache/helix/HelixManager.java
+++ b/helix-core/src/main/java/org/apache/helix/HelixManager.java
@@ -38,10 +38,11 @@ import org.apache.helix.store.zk.ZkHelixPropertyStore;
  * manager = HelixManagerFactory.getZKHelixManager(
  *    clusterName, instanceName, ROLE, zkAddr);
  *    // ROLE can be participant, spectator or a controller<br/>
+ * manager.addPreConnectCallback(cb);
+ *    // cb is invoked after a connection is established, but before the node of type ROLE
has
+ *    // joined the cluster. This is where one can add additional listeners (e.g manager.addSOMEListener(listener);)
  * manager.connect();
- * manager.addSOMEListener();
- * manager.start()
- * After start is invoked the subsequent interactions will be via listener onChange callbacks
+ * After connect is invoked the subsequent interactions will be via listener onChange callbacks
  * There will be 3 scenarios for onChange callback, which can be determined using NotificationContext.type
  * INIT -> will be invoked the first time the listener is added
  * CALLBACK -> will be invoked due to datachange in the property value


Mime
View raw message