The problem was that my hosting service was using log4j implementation for commons-logging in their tomcat, ofcourse they missed telling me that. So when I removed log4j jar from my webapp's WEB-INF/lib, I got rid of my initial error. I got into a whole different set of problems related to file permissions after that but that is another rant :-).
Thanks for your responses. Avilay Parekh On 7/6/06, Javier Gonzalez <[EMAIL PROTECTED]> wrote:
On 7/6/06, avilay parekh <[EMAIL PROTECTED]> wrote: > Apart from log4j-1.2.13.jar, are there any other jars that Logger would be > dependent on? Nopes. > A possiblity is that my desktop tomcat has some pre-installed jars that > might not be present on the hosting service's tomcat installation. I > guess all non java. classes could be candidates for this: > 20 import javax.jms > 10 import javax.mail I don't think that a normal tomcat install has either of those - those are j2ee apis, of which, AFAIK, tomcat only provides javax.servlet.* I don't know or remember about the other ones, but mail and jms caught my eye. -- Javier González Nicolini --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
