Hi Craig,

I know how to deploy pluto 1.1 to tomcat 5.5.9 manually. So if you would like to do that manually too, you may refer to the README file.

Manual Installation:

1/ cd to pluto project home and execute: 'mvn install'
2/ copy the following to <TOMCAT_HOME>/shared/lib. (In a clean tomcat installation, the shared/lib directory should be empty)
     - castor-0.9.6
     - portlet-api-1.0.jar
     - pluto-container-1.1-SNAPSHOT.jar
     - pluto-descriptor-api-1.1-SNAPSHOT.jar
     - pluto-descriptor-impl-1.1-SNAPSHOT.jar
3/ copy the following to <TOMCAT_HOME>/common/endorsed, and replace the original JARs.
     - xercesImpl-2.6.2
     - xmlParserAPIs-2.6.2
4/ copy the following to <TOMCAT_HOME>/conf/Catalina/localhost:
     - <PLUTO_HOME>/pluto-portal/src/main/resources/pluto.xml
     - <PLUTO_HOME>/pluto-testsuite/src/main/resources/testsuite.xml
5/ copy and rename the following to <TOMCAT_HOME>/webapps
    - pluto-portal-1.1-SNAPSHOT.war to pluto-portal.war
    - pluto-testsuite-1.1-SNAPSHOT.war to pluto-testsuite.war
6/ start tomcat and visit: http://localhost:8080/pluto/portal


Hope that helps.
Regards.

On 10/24/05, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:

I finally got the pluto-1.1 driver and testsuite built after making a couple of changes to the root pom.xml and the same file under pluto-testsuite that I've checked into SVN. But I haven't been successful in deploying them to Tomcat 5.5.9. Can someone help me with this issue? Specifically, I'd like to know where all the generated jar files should go? They all seem to end up in WEB-INF/lib of the pluto webapp, which raises classloader problems in Tomcat. I moved most of them over to  <TOMCAT_HOME>/shared/lib, but then I ran into an NPE in the test pages, which seemed to be related to a lost ServetContext for the testsuite webapp. (The NPE stack trace points to line 119 in org.apache.pluto.core.PortletDescriptorRegistry).

In addition, I moved the pluto.xml Tomcat web context descriptor into <TOMCAT_HOME>/conf/Catalina/localhost. Also, I changed the pluto-testsuite.war name to testsuite.war (and fixed this in its pom.xml). This allowed the testsuite's deployed context (/testsuite) to reflect what was in the portal driver config file (pluto-portal-driver-config.xml).

TIA
/Craig

--

ZHENG Zhong

1 Avenue Alphand
75116 Paris, France
+33 6 76 80 45 90

Reply via email to