Oh, sorry Glen I misunderstood what Azeez said. My +1 for removing the ContextManagerListener of Clustering not the ContextListener of Axis2. As you have mentioned having this ContextListeners will help us to cleanly capture context events of Axis2. So I think our clustering impl should use that.
Chamikara On 5/29/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
Hi Afkham! Afkham Azeez wrote: > Hi Glen, > When I checked the logs, I found that you have introduced this > interface. What is the usage of this interface? This was added because we refactored ContextFactory away - and the reason for ContextFactory was to have one place that we could be notified of all the *Context creations (even though it never actually did that!). See thread at http://marc.info/?l=axis-dev&m=117822877408932&w=2. Apparently no one integrated this into the actual clustering code. > In the clustering implementation, we need to track the add context & > remove context events for service group contexts & service contexts. > Currently we are directly calling cluster manager from the relevant > places. Can this interface be adopted by the clustering implementation? Well, that was the idea... :) Do whatever the right thing is. If you feel you're getting good mileage out of the current code and there isn't too much tight coupling, feel free to remove ContextListener and associated APIs. Otherwise feel free to utilize it. Thanks, --Glen > On 5/28/07, *Afkham Azeez* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > wrote: > > The ContextListener interface is not used by the clustering > implementation. We directly call ContextManager.addContext() from > the relevant places. > Is this interface intended for any other purpose? Shall we remove it? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Chamikara Jayalath WSO2 Inc. http://wso2.com/ http://wso2.org/ - For your Oxygen needs
