Hi, I have recently tried Cocoon2 (with Tomcat 3.2.1, Slackware Linux, Apache 1.3.*) and got everything to work. That is, it was no problem to read http://localhost/cocoon. I did not modify any of the existing configuration files of Apache or Tomcat, when installing cocoon2. I have used in the past cocoon1 quite extensively and tried, among other things, XSP. This all worked very nicely. For that purpose, I had a separate context under webapps (say webapps/Foo). All my own xml related stuff was put into that directory. It should be possible with cocoon2 to do the same thing, but up till this very moment I had no success. While http://localhost/Foo displays the content of that directory, I cannot get the sitemap compiled so that a pipeline would start. Putting one of my own files (say foo.xml) into the webapps/cocoon directory and modifying the sitemap, so that the pattern foo would start a pipeline that transforms foo.xml into html, worked without problems. Which files/directories in webapps/foo from cocoon2 should always be there: cocoon.xconf, sitemap.xmap and WEB-INF? The web.xml should contain cocoon2 specific entries? What are the minimal entries in the cocoon.xconf and sitemap.xmap? I have copied these files from the webapps/cocoon subdirectory (including the modified sitemap for foo that worked fine in webapps/cocoon). After restarting tomcat and apache, cocoon2 is telling me that it cannot find resource http://localhost/Foo/foo. What am I missing? Is there anything that should modified in the configuration files of Tomcat? Thanks for your help. -- Andre H. Juffer | Phone: +358-8-553 1683 The Biocenter and | Fax: +358-8-553-1141 the Dep. of Biochemistry | Email: [EMAIL PROTECTED] University of Oulu, Finland | WWW: http://www.biochem.oulu.fi/tutkimus/Biocomputing/ --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
