Anthony Bull wrote: > > Its better to use commons-logging 1.1.1 as from memory 1.0.4 has a > problem that causes Tomcat to not shutdown properly on some platforms. >
Yes, I was expecting that version 1.1.1 would be better than 1.0.4. Generally newer versions are better than older versions, unless the new one introduces a new bug :) But when I replace the version 1.0.4 of commons-loggins-api, located in the [CATALINA_HOME]/bin/ directory of Tomcat 5.0.28, by the newer version 1.1.1, without forgetting to rename the jar file to "commons-logging-api.jar", due to this file name be hardcoded in Tomcat, the Axis2 context is not being initialized, and I do not know why! Anything else is being correctly initialized (the Tomcat itself and all the rest of the contexts), except the axis2 context. For me that's a really strange, unexpected, and illogical behavior. Axis2 is supposed to work with the version 1.1.1 of commons-logging API, then why isn't its context being initialized? I don't know, but I suspect Axis2 uses the "commons-logging-1.1.1.jar" file located in the [CATALINA_HOME]/webapps/axis2/WEB-INF/lib/ directory, and ignores the one located in the [CATALINA_HOME]/bin/. But, if that's true, then how does Axis2 do such a thing? If my assumptions are correct, then how is Axis2 capable of ignoring the classloading mechanism of Tomcat? I've already tried to delete the "commons-logging-1.1.1.jar" jar file from the [CATALINA_HOME]/webapps/axis2/WEB-INF/lib/ directory, so that the only possible location of commons-loggin API is the one located in the [CATALINA_HOME]/bin/, but this attempt was unsuccessful. You can try all these things, and you can check for yourself that what I am saying is unfortunately true. Anyway, the most strange thing is that when I try to make the commons-logging-api located in the [CATALINA_HOME]/bin/ equal to the one located in the [CATALINA_HOME]/webapps/axis2/WEB-INF/lib/ (both equal to the version 1.1.1) the axis2 context is not being initialized. For me, the logical and expected behavior is exactly the opposite! There aren't logical reasons that explain why axis2 context is not being initialized. Thanks. -- View this message in context: http://www.nabble.com/Axis2-and-Tomcat-5.0.28-commons-logging-api-tp19242773p19252397.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
