But with new aspectized deployers, this approach cannot work.
As you actually don't know which all config files are valid in some
metadata location.
e.g. WEB-INF/my-custom.foo is completely valid if I have a *.foo
matching deployer
Then wouldn't looking into just redeploy on root dir touch to
make this
simpler for users ?
Or does the touch of descriptors allow for partial deployment, if yes
are they useful ?
/max
It is now responsibility of the StructureModificationChecker to
recognize changes.
It mostly boils down to SMC's filter to know which files to monitor.
One solution would be to have a filter which would do incallback on
FileMatcher,
which is what all sub-AbstractVFSParsingDeployer deployers implement.
This would probably catch most of the config use cases.
e.g. you could easily by-pass it by not extending
AbstractVFSParsingDeployer or not implementing FileMatcher on your
custom deployer
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development