On Mon, 2002-11-11 at 17:38, Geoff Howard wrote: > This sounds like it's just a configuration problem > causing unpacking cocoon.war to fail. Also, unless > you left some steps out of your install notes, you're > going to have problems once things get up and running > due to the outdated parser that ships with jdk 1.4 > (unless that no longer holds for 1.4.1) see the 1.4 > specific instructions at > http://xml.apache.org/cocoon/installing/index.html
I thought that the cvs version would work with the latest JDK, which I believe is 1.4.1. Should we really use an older JDK? > First, confirm that cocoon.war really does have the > file it's looking for. jar tvf cocoon.war | grep > MANIFEST.MF Yes, it does. > Check file permissions to make sure that the tomcat > user has all permissions necessary to expand the war, There is no tomcat user. The directory seems to be owned by tomcat4, though there is no such user. Maybe that's normal. I gave write access to that user (actually I change a few access rights until I got this right, so it might take more than that.) and that seems to fix it. Now I get the "javax.servlet.ServletException: Servlet.init() for servlet Cocoon2 threw exception" error. I guess that's connected to the JDK 1.4.1 problem mentioned above, which I should be able to deal with. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
