Actually if it has worked before I'm not sure. My initial email assumed
that Pluto 2 and 1.1 have the same classloader needs and I honestly
thought they did. What I have for my shared loader config is:
shared.loader=${catalina.base}/shared/classes,${catalina.base}/shared/lib/*.jar
-Eric
michael freedman wrote:
> Thanks. What should I set the shared.loader setting to? Also what is
> different from the Pluto 2.0 in February 2008 and now as that one
> runs fine in an Apache 6.0.16 environment without shared.loader being
> set to anything.
> -Mike-
>
>
> Eric Dalquist wrote:
>> You need to edit conf/catalina.properties and enable the shared
>> classloader. Tomcat 6 by default doesn't enable a classloader for
>> shared/lib where Pluto needs to put its JARs.
>>
>> -Eric
>>
>> michael freedman wrote:
>>> Any advice? I have an installation of Pluto 2.0 + Tomcat 6.0.16
>>> from back in the spring that works fine. Now I am trying to install
>>> the latest Pluto 2.0 into either a new Tomcat 6.0.16 or Tomcat
>>> 6.0.18. All seems to install okay (based on the information from
>>> the Pluto website). However Pluto doesn't start -- becaused it
>>> throws a noClassDefFound exception for the class:
>>> org.apache.pluto.driver.PortalStartupListener. Checking the various
>>> config files makes it look like things are set up right. And of
>>> course this class exists in the
>>> pluto-portal-driver-2.0.0-SNAPSHOT.jar that is found in the
>>> web-inf/lib dir of the pluto (installed) webapp. Has anyone seen
>>> this/or have ideas on what I can check/try?
>>> -Mike-