https://issues.apache.org/bugzilla/show_bug.cgi?id=54386
--- Comment #5 from Peter Rader <p.ra...@gmx.net> --- @Kolinko You are right, /work or /temp is the even better approach, that was my idea too! Redeployment may overwrite existing exploded jar-resources and we must prevent persistent-session injection. So there should be a whole folder-structure unique to the domain/context (in example tomcat/work/resources/localhost/petshop/)! @Schultz Yes we can solve this via ant, but this always would be complex and dirty hack. Im not sure what if *two* jars contains different files but same *file-names*, which should be used? So there are some ant-tasks: 1. The webapp/ant must introspect the class-loader and 2. the class-load-order which jar would be load first, the shared/lib and bootstrap and combined and the systempath up to JRE/JDK. Another workaround is to write a lifecycle-listener who knows all the resources an explode them at deployment. Ok we are at least now able to say: this is the subtask of the CDN's-jar (so it will be an Wontfix too). -- 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
