[ 
https://issues.apache.org/jira/browse/AXIS2-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975980#action_12975980
 ] 

Afkham Azeez commented on AXIS2-3844:
-------------------------------------

Andreas, Amila,
I'm seriously offended by your suggestion that I'm trying to promote my blog 
through the code I've written. Here is the full comment in the 
org.apache.axis2.clustering.ClusteringAgent interface. This comment refers to 
"static membership configuration". To describe the concept of different 
membership schemes, I have referred to 
http://blog.afkham.org/2008/05/group-membership-management-schemes.html. 

* <p>
 * This is the main interface in the Axis2 clustering implementation.
 * In order to plug-in a new clustering implementation, this interface has to be
 * implemented.
 * </p>
 * <p>
 * The initilization of a node in the cluster is handled here. It is also 
responsible for getting
 * this node to join the cluster. This node should not process any Web services 
requests until it
 * successfully joins the cluster. Generally, this node will also need to 
obtain the state
 * information and/or configuration information from a neighboring node.
 * This interface is also responsible for
 * properly instantiating a {...@link 
org.apache.axis2.clustering.state.StateManager} &
 * {...@link org.apache.axis2.clustering.management.NodeManager}. In the case of
 * a static <a 
href="http://blog.afkham.org/2008/05/group-membership-management-schemes.html";>
 * membership scheme</a>,
 * this members are read from the axis2.xml file and added to the 
ClusteringAgent.
 * </p>
 * <p>
 * In the axis2.xml, the instance of this interface is specified using the 
"clustering"
 * class attribute.
 * e.g.
 * <code><b>
 * <nobr>&lt;clustering 
class="org.apache.axis2.clustering.tribes.TribesClusterAgent"&gt;</nobr>
 * </b>
 * </code>
 * specifies that the TribesClusterAgent class is the instance of this 
interface that
 * needs to be used.
 * </p>
 * <p>
 * There can also be several "parameter" elements, which are children of the 
"clustering" element
 * in the axis2.xml file. Generally, these parameters will be specific to the 
ClusteringAgent
 * implementation.
 * </p>


Similarly, in org.apache.axis2.clustering.management.NodeManager, I have 
referred to High Availability. 
http://blog.afkham.org/2008/05/definition-of-high-availability.html. The full 
comment is as follows:


/**
 * <p>
 * This interface is responsible for handling configuration management. 
Configuraion changes include
 * <p/>
 * <ul>
 * <li>Rebooting an entire cluster, in which case, all nodes have to load the 
new Axis2 configuration
 * in a consistent manner
 * </li>
 * <li>
 * Deploying a new service to a cluster or undeploying a service from a cluster
 * </li>
 * <li>
 * Changing the policies of a service deployed on the cluster
 * </li>
 * </ul>
 * </p>
 * <p>
 * It is not mandatory to have a NodeManager in a node. In which case the 
cluster may be
 * used only for <a 
href="http://blog.afkham.org/2008/05/definition-of-high-availability.html";>
 * High Availability</a> through context replication. However, it is difficult 
to imagine that
 * a cluster will be deployed in production with only context replication but 
without cluster
 * configuration management.
 * </p>
 * <p>
 * The implementation of this interface is set by the
 * {...@link org.apache.axis2.deployment.ClusterBuilder}, by
 * reading the  "configurationManager" element in the axis2.xml
 * <p/>
 * e.g.
 * <code>
 * <b>
 * <configurationManager 
class="org.apache.axis2.cluster.configuration.TribesConfigurationManager">
 * </b>
 * </code>
 * </p>
 */

Similarly, in org.apache.axis2.clustering.state.StateManager I have referred to 
HA & scalability. If you would take the trouble to carefully read the full 
comment, you would see that I have also referred to 
http://www.ibm.com/developerworks/webservices/library/ws-apacheaxis2.

/**
 * <p>
 * This interface is responsible for handling context replication. The property 
changes in the
 * <a 
href="http://www.ibm.com/developerworks/webservices/library/ws-apacheaxis2/";>
 * Axis2 context hierarchy
 * </a> in this node, are propagated to all other nodes in the cluster.
 * </p>
 * <p>
 * It is not mandatory to have a StateManager in a node. If we are not 
interested in
 * <a 
href="http://blog.afkham.org/2008/05/definition-of-high-availability.html";>
 * High Availability</a>, we may disable context replication by commenting out 
the "contextManager"
 * section in the axis2.xml cluster configuration section. In such a scenatio, 
the cluster will be
 * used only for the purpose of
 * <a 
href="http://blog.afkham.org/2008/05/definition-of-scalability.html";>Scalability</a>
 * </p>
 * <p>
 * The implementation of this interface is set by the
 * {...@link org.apache.axis2.deployment.ClusterBuilder}, by
 * reading the  "contextManager" element in the axis2.xml
 * <p/>
 * e.g.
 * <code>
 * <b>
 * <contextManager 
class="org.apache.axis2.cluster.configuration.TribesContextManager">
 * </b>
 * </code>
 * </p>
 */

So, the accusation that the both of you (Andreas & Amila) are trying to make 
have no basis whatsoever, and it is saddening to learn that you guys would make 
such an accusation at a fellow dev without even reading through the relevant 
code comments.


> kernel clustering code Javadoc has pointers to blog entries.
> ------------------------------------------------------------
>
>                 Key: AXIS2-3844
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3844
>             Project: Axis2
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: nightly
>            Reporter: Tom Seelbach
>            Priority: Minor
>
> Afkham,
> In the javadoc for kernel/.../clustering/ ClusterManager, 
> ConfigurationManager, and ContextManager there are pointers to some 
> definitions in your blog.  If these definitions are important for describing  
> the clustering function then they should be somewhere on  the Axis2 site, or 
> just inline.   If the blog goes away the links would be broken.
> thanks,
> Tom
> src/org/apache/axis2/clustering/ClusterManager.java: * a static <a 
> href="http://afkham.org/2008/05/group-membership-management-schemes.html";>
> src/org/apache/axis2/clustering/ClusterManager.java:     * <a 
> href="http://afkham.org/2008/05/group-membership-management-schemes.html";>
> src/org/apache/axis2/clustering/ClusterManager.java:     * <a 
> href="http://afkham.org/2008/05/group-membership-management-schemes.html";>
> src/org/apache/axis2/clustering/configuration/ConfigurationManager.java: * 
> used only for <a 
> href="http://afkham.org/2008/05/definition-of-high-availability.html";>
> src/org/apache/axis2/clustering/context/ContextManager.java: * <a 
> href="http://afkham.org/2008/05/definition-of-high-availability.html";>
> src/org/apache/axis2/clustering/context/ContextManager.java: * <a 
> href="http://afkham.org/2008/05/definition-of-scalability.html";>Scalability</a>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to