The deployment order should not be significant, unless there is a huge delay between copying two files, but in that case, trying to order the bundles won't matter, since some won't be available at all. If that's not the case, I would think this is a bug.
The main reason is that all bundles are installed before being started, so you should not have any resolution problems, since all the bundles will be installed when the first one is resolved. 2010/3/10 Peter Gardfjäll <[email protected]>: > Hi, > > I've been experimenting some with writing a custom ArtifactInstaller > to extend the functionality of FileInstall. > As part of this effort, I have observed that the directory watcher > processes the files in the deployment/load directory in no particular > order. > I was thinking that since deployment order quite often is important > (at least judging from my experience), would it make sense to have the > directory watcher process files in an "oldest-first" manner (or at > least make the processing order configurable to some extent)? > This would prevent resolution problems for those cases where > bundles/artifacts have been copied to the "pickup directory" in > correct dependency order. > > Does it sound reasonable? If so, I can file a Jira issue. > > best regards, Peter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
