Hey David, I was wondering if you already had a workable solution for the MBean registration issue? I was thinking instead of putting the code in the AsyncBaseLifecycle it should instead go in the base MBean code. I'll raise a JIRA issue and we can continue discussion of it.
Grant ---------- Forwarded message ---------- From: Guillaume Nodet <[EMAIL PROTECTED]> Date: Mar 17, 2007 9:40 AM Subject: Re: Websphere 6.1 and MBean registration issue To: [email protected] On 3/16/07, Grant M <[EMAIL PROTECTED]> wrote:
Hi, I've been out of touch for a while with swapping to a new job and all and I was wondering whether David Potter had forwarded a solution to the MBean registration issue in Websphere? If not I'd like to open the floor to discussions on a possible fix.
I don't think so, but you should ping him and cc this list to see if he has worked on it already. I think the possible use of querynames could be fraught with issues
especially in clustered environments. Would it be possible to change the base MBean itself so that upon registration it updated the objectName? That way changes would be propagated correctly? I noticed in the code there is references to property change listeners and was wondering whether this meant it was already implemented?
Yeah, it should be possible to retrieve the new value of the Objectname and use it instead of the one ServiceMix generates. I think this is the only change to make, but i may miss something: where do you want to propagate the change ? Anyway, property change listeners should generate jmx notifications, provided that the setter call the needed method of course. Cheers,
Grant M
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
