> I put all the libratries of pluto in the tomcat common/lib dir.... > > aopalliance-1.0.jar > commons-beanutils-1.7.0.jar > commons-digester-1.8.jar > commons-el.jar > commons-fileupload-1.1.1.jar > commons-io-1.3.1.jar > commons-io-1.3.jar > commons-logging-api-1.1.jar > jasper-compiler.jar > jasper-compiler-jdt.jar > jasper-runtime.jar > jsp-api.jar > jstl-1.0.6.jar > jstl.jar > naming-factory.jar > naming-factory-dbcp.jar > naming-resources.jar > pluto-portal-driver-1.1.4.jar > pluto-portal-driver-impl-1.1.4.jar
Also put pluto-descriptor-api.jar and pluto-descriptor-impl.jar, as well as pluto-container.jar. You'll also want pluto-taglib.jar (or whatever its called), but that can go in you're web app if you'd prefer. Also, as a troubleshooting measure, try defining your web.xml as a servlet 2.3 application descriptor. Pluto might be freaking out over this... technically, a JSR 168 container is only required to support servlet 2.3, so you should plan your project implementation accordingly unless you know that your target platform supports a higher level of the spec. I've used this configuration in both Tomcat and Jetty and it works fine once you have all your JARs in the right place. -- Ben
