Ivan, thanks for the pointer. I was able to fix the issue by adding the following to the deployment plan:

<hidden-classes>
<filter>org.apache.geronimo.kernel.log.GeronimoLogFactory</filter>
<filter>META-INF/services/org.apache.commons.logging.LogFactory</filter>
</hidden-classes>
<inverse-classloading/>

Note that, even with the class filters, I had to add the <inverse-classloading/> property to prevent commons logging from picking up GeronimoLogFactory from the parent classloader.

Anil Chawla


Inactive hide details for Ivan ---08/19/2010 09:36:46 PM---Hi,     Refer to this thread, it should be helpful.Ivan ---08/19/2010 09:36:46 PM---Hi, Refer to this thread, it should be helpful.


From:

Ivan <xhhsld@gmail.com>

To:

user@geronimo.apache.org

Date:

08/19/2010 09:36 PM

Subject:

Re: Issue regarding GeronimoLog





Hi,
    Refer to this thread, it should be helpful.
   
http://apache-geronimo.328035.n3.nabble.com/Application-specific-log4j-issue-tc863758.html#a863758


2010/8/19 Anil Chawla <achawla@us.ibm.com>



--
Ivan