Thanks for the quick response. I was hoping I was just missing something obvious. Looking
at the code inside LifecycleAction, it looks like if I give a bogus method name, the
exception will be eaten and logged, so that should be viable workaround until a cleaner
solution is available.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045599#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...