Greg,

Try this: create a commons-logging.properties file somewhere in the
classpath
of your portlet. WEB-INF/class is favorite. Put this in there:

org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogg
er

Todd 

> -----Original Message-----
> From: Greg Reddin [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, July 25, 2006 8:31 PM
> To: MyFaces Discussion
> Subject: Re: Myfaces Portlets With Liferay and Maven
> 
> Thanks, Todd.  Here's the stack trace:
> 
> 03:23:44,545 ERROR [org.apache.catalina.core.ContainerBase] 
> Exception invoking periodic operation:
> java.lang.NoSuchMethodError: org.apache.log4j.Category.log(Ljava/lang/
> String;Lorg/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Th
> rowable;)V
>          at org.apache.commons.logging.impl.Log4JCategoryLog.error
> (Log4JCategoryLog.java:149)
>          at org.apache.catalina.core.StandardContext.listenerStart
> (StandardContext.java:3733)
>          at org.apache.catalina.core.StandardContext.start
> (StandardContext.java:4187)
>          at org.apache.catalina.startup.HostConfig.checkResources
> (HostConfig.java:1089)
>          at org.apache.catalina.startup.HostConfig.check
> (HostConfig.java:1187)
>          at org.apache.catalina.startup.HostConfig.lifecycleEvent
> (HostConfig.java:292)
>          at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
> (LifecycleSupport.java:119)
>          at org.apache.catalina.core.ContainerBase.backgroundProcess
> (ContainerBase.java:1305)
>          at org.apache.catalina.core.ContainerBase
> $ContainerBackgroundProcessor.processChildren(ContainerBase.java:1569)
>          at org.apache.catalina.core.ContainerBase
> $ContainerBackgroundProcessor.processChildren(ContainerBase.java:1578)
>          at org.apache.catalina.core.ContainerBase
> $ContainerBackgroundProcessor.run(ContainerBase.java:1558)
>          at java.lang.Thread.run(Thread.java:613)
> 
> This is what I have in WEB-INF/lib:
> 
> commons-beanutils-1.7.0.jar
> commons-codec-1.3.jar
> commons-collections-3.1.jar
> commons-digester-1.7.jar
> commons-el-1.0.jar
> commons-fileupload-1.0.jar
> commons-lang-2.1.jar
> commons-logging-1.0.4.jar
> commons-validator-1.1.4.jar
> jstl-1.1.2.jar
> myfaces-api-1.1.1.jar
> myfaces-impl-1.1.1.jar
> oro-2.0.8.jar
> tomahawk-1.1.1.jar
> util-jsf.jar
> xml-apis-1.0.b2.jar
> 
> It looks like the problem is with an incompatible version of log4j.   
> I have log4j 1.2.12 in common/lib/ext.
> 
> Greg
> 
> On Jul 25, 2006, at 1:34 PM, Papaioannou, Todd wrote:
> 
> > I have one there too, and also commons-logging-1.0.4.jar in my 
> > WEB-INF/lib folder. Everything works fine. Is there some 
> exception you 
> > are getting that might shed some more light?
> >
> > Todd
> >
> >> -----Original Message-----
> >> From: Greg Reddin [mailto:[EMAIL PROTECTED]
> >> Sent: Monday, July 24, 2006 3:18 PM
> >> To: MyFaces Discussion
> >> Subject: Re: Myfaces Portlets With Liferay and Maven
> >>
> >>
> >> On Jul 24, 2006, at 4:33 PM, Papaioannou, Todd wrote:
> >>
> >>> What version of Liferay are you using? With the LEP 4.0 you
> >> shouldn't
> >>> have to worry about the version of Myfaces LEP is using
> >> since this is
> >>> segrated into a different classloader. You are free to 
> put whatever 
> >>> version you want in your WEB-INF/lib folder. I am using 
> >>> MyFaces-1.1.4-SNAPSHOT and tomhawk-1.1.2 with no problems.
> >>
> >> I'm using Liferay Professional 4.0 - Tomcat version.  I found a 
> >> commons-logging.jar (version 1.0.4 according to the
> >> Manifest) in common/lib/ext.  If I remove it Liferay won't start 
> >> because some portlets die (including the main CMS portlet).
> >>
> >> Greg
> >>
> >>
> >
> 
> 

Reply via email to