> Was the scanner ever intended to watch a single deployable file? Or just > watch a directory containing deployable files?
The URLDeploymentScanner was designed to watch a list of one or more URLs. It also supports scanning for files in a directory for 'file' URLs. This means that the a directory URL would never have been propagated to the targer Deployer... only children of that directory. > If it was just for watching a directory, then I agree... this patch does not > belong here. In this case, a second scanner should be developed to just > deployable units (with no watching sub directories). If this is done, should > the current scanner be limited to only watching directories? Currently it > does monitor both. I am not sure what you mean here really. UDS scans for URLs not files or directories. You could even consider the file protocol bits a hack, though it is minor and isolated... and thus more of a feature. I am not really sure what this patch is trying to accomplish, though I have a rough idea. One of the big problems I have with this patch is that it now needs to do some thinking about what a deployment file is... when that is currently a logic function of the MainDeployer & SubDeployer interaction. > Let me know how to procede. Thanks. Could you explain to me what you are trying to accomplish, I might have some insights for how to better implement it... or not who knows. --jason ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
