"jaikiran" wrote : *by default* should we be really doing the guess work for redeployments or like AS-4.x only watch for known top level files | I already have this implemented, but I don't like the catch behind it. :-( We already have a notion of known file names, it's "hidden" under FileMatcher interface. Currently the only one's implementing it are exactly the parsing deployers that know certain configuration files == true candidates for re-deploy on change. But here comes the catch. :-) FileMatcher only works on VirtualFile, whereas in StructureCacheFilter we match against path. Hence I added PathMatcher interface, which is again currently only implemented by parsing deployers. And the catch is how to guarantee consistency between file and path matchers? A VFFilter and SCFilter for MetaDataStructureModificationChecker must filter the same resources, meaning sets of file and path matchers must be in-synch/consistent. Currently with only parsing deployers implementing those two interfaces, where I made the impls consistent, I don't see an issue, but if the user deploys any bean implementing either of those two interfaces, that bean will be automatically (via in-callback) part of filtering, hence potentially breaking consistency. Perhaps the solution is to change SCFilter to work against VF instead of just path. I'll check how much work it is to change this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249590#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...