https://bz.apache.org/bugzilla/show_bug.cgi?id=57129
--- Comment #16 from Philippe Busque <pbus...@mediagrif.com> --- We just begun converting your tomcat 6 and tomcat 7 Webfarm to Tomcat 8, and honestly, this is a show stopper for us. We cannot, in a cluster setup, start Tomcat and have each instance have a different class loading behaviour. This is especially important when serialization come into play with session sharing inside the cluster, where a class mismatch can lead to Serialization Exception. Or with logging libraries, such as logback, which override existing libraries with their own to offer a logging facade. In an ideal world, yes, we would have a nice war with no overriding classes, with no dependencies pulling deep libraries. In an ideal world, we would use absolute path for a PreResources. But this is not ideal. Maven-generated war with SNAPSHOT dependencies will have variables suffixes. Unless PreResources can support wildcards or prefixes in order to support versioning, this solution is not viable for most of us. There was a similar use case back in Tomcat 7, when the support for War outside the webapp support was dropped, but added back later with a flag. There exist applications that need a deterministic class loading. Heck, Java itself at it's core, is deterministic. That's the whole notion of classpath that is being ignored. If you do not want to make the jar sorting as the default behaviour, fine. But at the very least, offer it as an option for people to decide if they need it. ie <context jarloading="name|none|lastmodified" /> Thanks -- 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
