Hi Kenneth, (and all) Is there support for a war within a war? Due to a legacy cacheing system (created long before hibernate et. al.) I need/want my app to run within the same JVM as Axis 1.1 AND Axis 2.0. Because of this, I want BOTH the Axis 1.1 jar AND the Axis 2.0 jars distributed with the war which deploys our app...
Since they are in the same JVM, the class loader finds the first "Contants" class in the classpath and loads that up so that the referenced constant isn't found. I agree that if the two jars were in different webapps, there'd no problem as there'd be two separate JVM's and two separate classloaders, right? I guess I'm just surprised that no one spotted the name clash and if they did, decided it was ok... With the massive changes to the package and class names they've already made, I don't see why they just don't change the name of the class. Maybe I'm just not being clear. Thanks for everyone's attention and consideration, -Clint
