You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Elliot Metsger (JIRA)" <ji...@apache.org> on 2007/06/02 21:29:15 UTC
[jira] Resolved: (PLUTO-376) Update Pluto to work with Tomcat 6.x
[ https://issues.apache.org/jira/browse/PLUTO-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliot Metsger resolved PLUTO-376.
----------------------------------
Resolution: Fixed
> Update Pluto to work with Tomcat 6.x
> ------------------------------------
>
> Key: PLUTO-376
> URL: https://issues.apache.org/jira/browse/PLUTO-376
> Project: Pluto
> Issue Type: Improvement
> Components: maven pluto plugin
> Affects Versions: 1.2.0, 1.1.3
> Reporter: Elliot Metsger
> Assignee: Elliot Metsger
> Fix For: 1.2.0, 1.1.4
>
>
> Update Pluto to work with Tomcat 6.x.
> Most notably Tomcat 6.x does away with the classloader hierarchy <tomcat>/server, <tomcat>/common, <tomcat>/shared. Everything by default is lumped into <tomcat>/lib. The endorsed directory is now <tomcat>/endorsed.
> Perhaps related is that Pluto crash and burns when starting up in Tomcat 6:
> FINE: [3] Creating portlet container...
> Jun 2, 2007 2:10:42 AM org.apache.catalina.core.StandardContext listenerStart
> SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener
> java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
> at org.apache.pluto.PortletContainerFactory.<clinit>(PortletContainerFactory.java:36)
> at org.apache.pluto.driver.PortalStartupListener.initContainer(PortalStartupListener.java:180)
> at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:126)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
> Moving webapps/pluto/WEB-INF/lib/commons-logging-api-1.1.jar to lib/ solves the problem. I wonder if the thread that loads listener classes has <tomcat>/lib as its classloader versus <tomcat>/<webapp>/WEB-INF/lib
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.