Joerg Heinicke wrote:
On 29.08.2005 01:12, Peter Flynn wrote:
Umm...now that it's built OK, I moved webapps to tomcat/webapps/cocoon
and copied the xalan etc, and restarted tomcat, but tomcat says Servlet
Cocoon is not available.
<sigh/> It was sooo much easier with a .war file.
(Actually I meant, when the .war file was distributed <ducking> :-)
Why don't you do it that way then? ;-) "build war" creates a WAR file for
you.
Just did that. I was hoping it would work when I hit up localhost:8080
for the tomcat home page prior to trying localhost:8080/cocoon and the
disk light went on solid and I could hear the disk furiously working :-)
Tomcat unpacked the war file OK, but it still says
HTTP Status 404 - Servlet Cocoon is not available
type Status report
message Servlet Cocoon is not available
description The requested resource (Servlet Cocoon is not available) is not
available.
Apache Tomcat/5.0
Pity.
Another possibility - at least for introductory tests - is to use
Jetty: "cocoon servlet" on the command line.
There doesn't appear to be any command "jetty" nor any command "cocoon".
# jetty cocoon servlet
bash: jetty: command not found
# cocoon servlet
bash: cocoon: command not found
#
I'm sure I saw an explicit command to do this, in the docs or the wiki,
but I can't find it.
I didn't try it before, because I'm fairly confident that Cocoon itself
works once it's running :-) I've been using it since Cocoon-1, and my
problems have mostly been with getting it installed, not with running it
once it's in. And it's usually been my own ignorance that's to blame:
the docs are written for the Java expert, rather than the XML user.
///Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
