Bugs item #858412, was opened at 2003-12-11 18:08 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=858412&group_id=22866
Category: JBossServer Group: v3.2 >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Rodney Russ (rruss) Assigned to: Nobody/Anonymous (nobody) Summary: Change in URLDeploymentScanner behavior Initial Comment: In 3.0.2 the URLDeploymentScanner would deploy all components in a directory that was listed in the URL list (configured in jboss-service.xml) before deploying components of the next directory. This was accomplished in the scan method by passing off each directory found to the scanDirectory method. The scanDirectory method would find all deployable files, sort that list (with the configured sorter), then deploy all URL's in the list. In 3.2.3, this behavior was changed. All deployable URL's found in each URL configured in jboss-service.xml are added to a list, then that list is sorted. The effective behavior is to deploy in the sort order across all directories listed instead of within each directory listed. We are trying to upgrade from 3.0.2 to 3.2.3, and this change in behavior is breaking our deployment environment. We created multiple directories to account for some deployment dependencies with the understanding that the order in jboss-service.xml would affect deployment order. Could we either get an alternative URLDeploymentScanner that has the old behavior, or have an attribute that could be set in the URLDeploymentScanner mbean configuration in jboss-service.xml to preserve the old behavior? ---------------------------------------------------------------------- >Comment By: Adrian Brock (ejort) Date: 2004-03-06 13:56 Message: Logged In: YES user_id=9459 If you want this behaviour code it yourself and post it as a patch. We are unlikely to accept the attribute solution. Regards, Adrian ---------------------------------------------------------------------- Comment By: Sacha Labourey (slaboure) Date: 2003-12-12 08:39 Message: Logged In: YES user_id=95900 Let's not change that, it seems much more logical for me to first read all directories, sort the result, sort dependencies and then deploy. If you want another behaviour, simply add another URLDeploymentScanner definition AFTER the default one: they will deploy one after the other in this case. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=858412&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
