https://issues.apache.org/bugzilla/show_bug.cgi?id=57274
--- Comment #4 from Phillip <pverhey...@broadleafcommerce.com> --- The solution that I had was to completely disable the scanning by adding an empty <absolute-ordering /> tag into my web.xml. This obviously means that there is no way to have both my Spring/persistent unit class transformation along with the ServletContainerInitializers (not an issue in my case). I believe that one possible solution here would be to disable what I believe to be a performance improvement of loading the classes by the class loader. If the classes were not loaded by the classloader at all and instead every single class was loaded by the FileInputStream, then this would not be a problem at all. Perhaps there could be some sort of startup flag that controls whether or not to use the class loader to look for ServletContainerInitializers or to skip it and load all of them by FileInputStreams? Mark, what do you mean by "delay the transformation until the the class is declared"? Does this mean moving the transformation code from WebAppClassLoader to after it has retrieved the cache from resourceEntries, but prior to actually loading the class itself (like via a Class.forName())? This seems like a better solution to me. It seems there is a slight deviation by looking up a class by name with a getResourceAsStream() and referencing it by doing a Class.forName(). -- 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
