I am in the process of getting a new Cocoon2 installation running. I am
new to Cocoon. Using Tomcat 4, Java 3, Cocoon 2.0.1, Linux.

When I start Tomcat, its localhost_log.<date>.txt complains:

  2002-02-14 08:43:40 ContextConfig[/cocoon]: Missing application web.xml,
  using defaults only
[snip]
  2002-02-14 08:43:40 Internal Error: File /WEB-INF/web.xml not found

Indeed, I do not see the web.xml file in
  /usr/local/jakarta-tomcat-4.0.2/webapps/cocoon/WEB-INF/web.xml

although it is in cocoon.war and cocoon.war is in
  /usr/local/jakarta-tomcat-4.0.2/webapps/cocoon.war

When I manually extract web.xml from cocoon.war and put it in the WEB-INF
directory, the same log file has this error:

  2002-02-14 08:35:44 StandardWrapper[/cocoon:Cocoon2]: Marking servlet
  Cocoon2 as unavailable
  2002-02-14 08:35:44 StandardContext[/cocoon]: Servlet /cocoon threw
  load() exception
  javax.servlet.ServletException: Wrapper cannot find servlet class
  org.apache.cocoon.servlet.CocoonServlet or a class it depends on
[snip]
  ----- Root Cause -----
  java.lang.ClassNotFoundException: org.apache.cocoon.servlet.CocoonServlet
        at
  org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1394)
[snip]

I tried setting init-classloader to "false" in my version of web.xml; no
change in behavior.

I discovered this problem because I did not believe that Cocoon was
reading my sitemap file, and when I looked for log files reporting that
the sitemap had been read, I found that no "core" error logs were being
generated at all. The logkit.xconf file says that that log file should be
named
      <filename>${context-root}/WEB-INF/logs/core.log</filename>

but no WEB-INF/logs subdirectory has been created at all. (logkit.conf
doesn't seem to exist outside cocoon.war, either.)

What's going on?

Thanks,
Jessica


---------------------------------------------------------------------
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]>

Reply via email to