what do you mean by "existing" mbean? you can't modify the EARDeployer to handle this, you need to write your own mbean to handle this.
basically you create an mbean and register it w/ the EARDeployer w/ a filter so you only get the events you want. when the EARDeployer sends a notification, it will determine if you should get the message (via the filter) and if yes, your mbean will be notified. once your mbean is notified, it can invoke whatever methods are necessary to do the cleanup work. i've did some experimentation w/ this the other day to solve a problem i was having, but just opted for a custom deployer - so if you ask me more "specific" questions, i can continue to provide some support. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828684#3828684 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3828684 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
