I'm very close at getting the embedded Tomcat running from an Eclipse Maven project; the (hopefully final) issue I'm now facing is the fact that a class is being loaded by the WebappClassloader and in another execution path via the launcher classloader, which makes them two different classes and things go awry.
Tomcat of course is being started by Eclipse with a full classpath, and I 'forward' that classpath to the webapp. If I do not do that, the webapp won't find anything that is on that startup classpath, so apparently Tomcat's classloading setup completely ignores the initial classpath and replaces it with its own structure. Ok, but somehow they do get mixed up, otherwise I would not run into the situation described above. So I was thinking that I could try and figure out why one class is being loaded by the launcher, but I foresee a long and windy path, with a lot of different situations where this loading goes wrong. So instead of trying to solve the conflict at webapp level, I could move in another direction: in normal (non embedded) Tomcat installations you are allowed to put shared jars in Tomcat's lib folder. These are then accessible by all webapps. Is it possible to have embedded Tomcat make its classpath available to the webapps, or configure the classes-directories and jars resources at Tomcat level? Tom --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
