Alex S wrote:
Excellent Help Simon! Thanks very much indeed,
Yes, having copied the jar files accross, I ran the same command as last time and cocoon started building the samples file. I quit it because it was just a test, but I now feel pretty confident that I will be able to get it running with my own pipeline.
Also thanks ,again, for the future proofing with the information about the later versions of Cocoon. I could have been completely stumped again!
One very happy subscriber, ------ Alex.
Simon Mieth wrote:
On Sun, 15 Feb 2004 11:27:45 +0000 Alex S <[EMAIL PROTECTED]> wrote:
Hi Thanks for the reply. Yes that makes some sense. But I am still having dificulties. Something about CatalogManager.properties or server.properties can't be found .
a) I am now just going to try using the CL to pass in all
the arguments directly. easier for troubleshooting I
think. b) Also with a fresh build of cocoon 2.1. I am
working on Linux redhat 9 by the way.
Thus I will try to build the samples having added pattern welcome-test.html to the root sitemap instead of ""
because I do not know how to represent the latter as an
argument on the [EMAIL PROTECTED] cocoon-2.1]#
./cocoon.sh cli welcome-test.html -C
build/webapp/WEB-INF/cocoon.xconf -c build/webapp/ -w
../tmp/ -d ../tmp/docs/
Gives me this response on the command line:
Cannot find CatalogManager.properties
Exception in thread "main"
java.lang.reflect.InvocationTargetException
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Nati
ve Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodA
ccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Delegatin
gMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source) at
Loader.run(Unknown Source) at Loader.main(Unknown
Source)
Caused by: java.lang.NoClassDefFoundError: javax/servlet/http/HttpSessionBindingListener
at java.lang.ClassLoader.defineClass0(Native
Method)
Hi Alex,
the problem is the "java.lang.NoClassDefFoundError", the CatalogManager.properties and server.properties "not found" message is no problem, ignore this.
You must only "cp tools/jetty/lib/servlet*.jar build/webapp/WEB-INF/lib" in the cocoon-2.1 directory.
If you use the current-CVS-version or the cocoon-2.1.4, you can run in trouble again. The "portal-framework" and "portal"-block break the CLI. I'm not sure if it fixed now, the bug is still open in bugzilla. You have 2 options to solve this.
1.) Build cocoon without "portal" and "portal-fw"-block, by: copy blocks.properties to local.blocks.properties and edit this file: comment out the "exclude.block.portal-fw=true" and "exclude.block.portal=true" properties. Then rebuild cocoon.
2.) You can comment out in the portal-related-stuff in the
cocoon.xconf file. That is a little bit tricky, to find
components. Maybe it is a good idea to make a copy like
"cocoon-cli.xconf" and edit this file. Later you can use this file with the "-C
where/the/is/cocoon-cli.xconf"-switch
You dont need this if you use cocoon-2.1.3.
I hope that helps. ;-)
Best Regards,
Simon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
