https://bz.apache.org/bugzilla/show_bug.cgi?id=57129
--- Comment #24 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to Sebastien Tardif from comment #23) > It seems this issue is about fundamentalist versus pragmatism. Even if the > order is deterministic, some application will still fail because not the > order they are used to, but at least always fail. > > I hate when things are random and I try to compare logs file, it's a pain. > Just for that reason I would have fixed this. > > I can tell you that my organization spent so far at least $3000 USD in lost > of time due to this. > > I learned in 3rd grade high school that probability of success get lower > fast if you have many tiny problem that doesn't seem useful to fix by > themselves. > > My app is like 10 years old, with many millions line of code, coded by 100+ > developers. While I did not perform an exhaustive search, I know of no servlet container which explicitly guarantees JAR-file load-ordering within a particular directory. Yes, WEB-INF/classes will be loaded before WEB-INF/lib/*.jar but there is no explicit guarantee of the ordering among the JAR files. The servlet spec also does not mandate any JAR-load-ordering. I actually support the idea of alphabetical JAR-load-ordering if for no other reason than it allows you to patch a server by dropping a new JAR file into WEB-INF/lib and starting the context. If that option is not available, you need to use container-specific features such a Tomcat's <PreResources>, etc. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
