because the commons-logging.jar is apparently in the system classpath, due to the way Java classloader delegation works, any log4j classes at the web application level are not visible to the logger factory by default.
prefer application level classes over system level classes
But did you answer my problem? I did not get it. Please explain if you can.
Deepak Bala wrote:Something like this -> https://coderanch.com/forums/posts/list/478489#2154062
sam bartl wrote:
Deepak Bala wrote:Something like this -> https://coderanch.com/forums/posts/list/478489#2154062
I am having the same problem , mine is a ear file , the solution weblogic.xml with preferred-web-inf-classes is suggested for a war file but what about ear file , I tried adding webloigc-application.xml but did not help , please advice me please help me , appreciate all your help.
sam bartl wrote:
sam bartl wrote:
Deepak Bala wrote:Something like this -> https://coderanch.com/forums/posts/list/478489#2154062
I am having the same problem , mine is a ear file , the solution weblogic.xml with preferred-web-inf-classes is suggested for a war file but what about ear file , I tried adding webloigc-application.xml but did not help , please advice me please help me , appreciate all your help.
here more description of m problem,
this is the exception I get
my weblogic-application.xml has the follwoing entries,
I started getting this exception after I added opensaml.
I think this is just classloading issue , Weblogic gurus please help me.
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |