The reason I mention using a different api, beside "ease of use" is that currently the filters are only currently invoked to check whether the vist() callback should be invoked, so introducing a different api for the new behaviour with a backward compatiblity method | /** | * Visit the resources in this module | * using the given filter | * | * @param visitor the visitor | * @param filter the filter | */ | public void visit(ResourceVisitor visitor, ResourceFilter filter) | { | - throw new UnsupportedOperationException("The module " + getContextName() + " does not support filtering: " + getClass().getName()); | + visit(visitor, filter, null); | } | would also avoid unintended changes to existing code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164736#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...