"kibbles" wrote : 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. Yes. :-) | try | { | ClassLoader cl = Configurator.getClassLoader(metaData); | joinpoint = configurator.getMethodJoinPoint(info, cl, method, parameters, false, true); | } | catch (JoinpointException ignored) | { | if (trace) | { | if (parameters == null) | log.trace("No " + method + " method for " + context); | else | log.trace("No " + method + parameters + " method for " + context); | } | return; | } | Will look at this issue ASAP. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045601#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...