> How about if there are 2 properties on the scanner: a list of single urls, > that can be packages or directories, and a list of directories to scan? > Then the user has to decide what they are trying to do;-)
This seems silly... but if you want todo this, make another scanner impl. If you notice the DeploymentScanner interface knows nothing about URL lists, files or directories. This was on purpose, as I have no idea what types of scanning input an impl might need (as this is a good example of... and I still have no idea what it is trying todo exactly). I do not believe that UDS or any DS should try to include monolithic functionality. Just create another DS and put the functionality there. It is simple to add another DS impl, by extending AbstractDeploymentScanner and implement scan()... or you can extend UDS if that would be easier. Perhaps once I see the DS code I will understand better. --jason ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
