Bugs item #711341, was opened at 2003-03-28 14:48 Message generated for change (Comment added) made by tstanczak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=711341&group_id=22866
Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Srivatsan (srivatsanp) Assigned to: Nobody/Anonymous (nobody) Summary: IncompleteDeployment Exception Initial Comment: Hi, When I use URLDirectoryScanner instead of URLDeploymentScanner, it throws IncompleteDeployment Exceptions. Jboss version is 3.2.0RC4 ---------------------------------------------------------------------- Comment By: Tomasz Stanczak (tstanczak) Date: 2003-09-26 16:14 Message: Logged In: YES user_id=757539 "URLDeploymentScanner must be used" why? if a particular deployment scanner is being offered in the jboss-service.xml file being part of the official distribution, then it should be all right to use it. Otherwise it shouldn't have been included in JBoss at all in the first place. Since it is there I take it for granted that I may use it if I have reasons to do so. Such a reason can be found in the comments around the scanner: "URLDeploymentScanner assumes that all directories are to be scanned, which can cause problems if directory referred to in the deploy attribute is an exploded archive" We do have exploded archives. The next reason is that I want to be able to set the order of deployment (I have inherited EmbeddedCatalinaService41, so want to deploy my classes before jbossweb-tomcat.sar gets loaded), I want it to be easy - without the need to code a directory sorter and/or use numbers in the file names. URLDirectoryScanner deploys files in the order they are specified in the URL list, which is good for me. The only problem is that it throws exception during deployment, the same exceptions that URLDeploymentScanner catches and leaves for the end of the deployment process, to see then if all deployments are all right. Since it can't resolve all the dependencies immediately it seems sensible to do so. I have modified URLDirectoryScanner along the lines of URLDeploymentScanner - it was quite easy, I have also found a similar patch here on SF done by someone else. I see no reason why it shouldn't be done - again, either URLDirectoryScanner shouldn't be used and the should be removed from JBoss, or it may be used, in which case this small but nerving annoyance should be removed. Please notice that nobody requires you to find a solution and code something - the patch is already in SF, and if you like I can include the code done by myself. See also bug# 684594. ---------------------------------------------------------------------- Comment By: Sacha Labourey (slaboure) Date: 2003-05-02 19:23 Message: Logged In: YES user_id=95900 URLDeploymentScanner must be used ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=711341&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
