Re: from sumit sanwal==
Hi,This in not a cocoon specific issue, I think.You can configure Tomcat to use a webapp located somewhere else that its webapps directory.To do this you need to edit Tomcat's server.xml file located in the conf directory.Make sure you have the following Connector enabled (it's enabled by default): port="8080" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="100" debug="0" connectionTimeout="2" useURIValidationHack="false" disableUploadTimeout="true" />Then change the default Host to something like: unpackWARs="true" autoDeploy="false" liveDeploy="false"> directory="C:/www/myproject/logs" prefix="tomcat." suffix=".log" timestamp="true"/> debug="0" saveOnRestart="false" maxActiveSessions="-1" minIdleSwap="-1" maxIdleSwap="-1" maxIdleBackup="-1"> Now put your cocoon stuff directly inside C:/www/myproject/webapp (no subdirectory, so the WEB-INF directory is directly under webapp) and you can access your application by callinghttp://localhost:8080/Hope this helps. (I've used Tomcat 4.1 for this. I'm not sure if Tomcat 5's config has changed.)FreekOn 3-jan-2006, at 13:02, Antonio Gallardo wrote:Sumit wrote: How could I have my Cocoon app located in a directory other than $TOMCAT_HOME/webapps/cocoon/? It is related the tomcat context concept. A hint can be found here: http://wiki.apache.org/cocoon/BeginnerDefaultContextMaybe it does not fully answer your question, but hope this helps.Best Regards,Antonio Gallardo.-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
LOW ON THREADS
I have recently installed cocoon 2.1.8 and now as soon as I use cocoon, in the message window of cocoon, I get an event ... EVENT LOW ON THREADS... and then ... WARN! No thread for Socket and ... WARN! OUT OF THREADS and all is very slow. Has someone something to help me? -- Jean-Claude Moissinac Department of Computer Science and Networks ENST Paris FRANCE E-mail: [EMAIL PROTECTED] Tel: (+33) 1.45.81.80.88 Fax: (+33) 1.45.81.71.58 http://shadok.enst.fr/jcm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Strange Pluto+Tomcat Realm mixture
Hi,
It seems i get interferances between some security-constraint in Tomcat
Realm and Pluto :
==> catalina.out <==
element "security-constraint" occurs more than once. (parent class:
org.apache.cocoon.portal.pluto.om.WebApplicationDefinitionImpl)
location: /web-app/security-constraint{file:
file:/opt/apache-tomcat-5.5.12/webapps/cocoon/WEB-INF/web.xml; line:
632; column: 24}
As i use Portal but not Pluto I removed pluto.jar and pluto from
cocoon.xconf, but the message is still there, any idea?
Phil
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: 2.1.8 Build Failed. Cannot find file validate-build.xml.
Nothing I reckon. Neither are 98ecb00c42ed41525cb6f098eacf76e5 is all I am saying. I suppose since both mirrors gave me the same file then it is unlikely that the first mirror had a bad file. More likely the fault is at my end. Cheers Russell -Original Message- From: Torsten Curdt [mailto:[EMAIL PROTECTED] Sent: 03 January 2006 12:44 To: users@cocoon.apache.org Subject: Re: 2.1.8 Build Failed. Cannot find file validate-build.xml. >> 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz >> 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz Copy-and-paste error? ..or what am I missing here? cheers -- Torsten The Information contained in this e-mail message is intended only for the individuals named above. If you are not the intended recipient, you should be aware that any dissemination, distribution, forwarding or other duplication of this communication is strictly prohibited. The views expressed in this e-mail are those of the individual author and not necessarily those of LINK Interchange Network Ltd. Prior to taking any action based upon this e-mail message you should seek appropriate confirmation of its authenticity. If you have received this e-mail in error, please notify the sender immediately. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.1.8 Build Failed. Cannot find file validate-build.xml.
Russell Brown wrote: That might be my problem:- $ md5sum cocoon-2.1.8-src.tar.gz 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz I tried another mirror and got $ md5sum cocoon-2.1.8-src.tar.gz 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz This time. Erm.. Is it me ? I am downloading the tar.gz as my office "security" forbids .zip files (I don't know why). Probably because of viruses. Now many corporate filters are stupid, and you sometimes can fool them by adding a query parameter to the URL, e.g. "http://.../cocoon-2.1.8-src.zip?foo=bar.txt";. Sylvain -- Sylvain WallezAnyware Technologies http://bluxte.net http://www.anyware-tech.com Apache Software Foundation Member Research & Technology Director - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 2.1.8 Build Failed. Cannot find file validate-build.xml.
Yes. The proxy will be at fault. Many thanks for your help. Now I have one more thing to check before I ask for help (which is good) Regards Russell -Original Message- From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED] Sent: 03 January 2006 12:30 To: users@cocoon.apache.org Subject: Re: 2.1.8 Build Failed. Cannot find file validate-build.xml. Le 3 janv. 06, à 13:15, Russell Brown a écrit : > That might be my problem:- > > $ md5sum cocoon-2.1.8-src.tar.gz > 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz > > I tried another mirror and got > > $ md5sum cocoon-2.1.8-src.tar.gz > 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz > > This time. Erm.. Is it me ? I am downloading the tar.gz as my office > "security" forbids .zip files (I don't know why). You can find the md5sum at http://cocoon.apache.org/mirror.cgi as well, it's the same that I put in my previous message. Technically it is possible that files might be incorrect on mirrors, but weirdnesses in proxy/firewall handling are more likely IMHO. -Bertrand The Information contained in this e-mail message is intended only for the individuals named above. If you are not the intended recipient, you should be aware that any dissemination, distribution, forwarding or other duplication of this communication is strictly prohibited. The views expressed in this e-mail are those of the individual author and not necessarily those of LINK Interchange Network Ltd. Prior to taking any action based upon this e-mail message you should seek appropriate confirmation of its authenticity. If you have received this e-mail in error, please notify the sender immediately. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.1.8 Build Failed. Cannot find file validate-build.xml.
067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz Copy-and-paste error? ..or what am I missing here? cheers -- Torsten PGP.sig Description: This is a digitally signed message part
RE: Problem writing generator
Marcel, First of all, shouldn't you set in handler.startElement(null, "exception", "exception", null); the namespace, so I18nTransformer.I18N_NAMESPACE_URI instead of null ??? Probably I am missing something? Furthermore, use log transformer http://cocoon.apache.org/2.1/userdocs/log-transformer.html for debugging. If you put it after your generator, you get a log of the sax events, so you see where it goes wrong AS > > Thanks Bertrand and Geert for answering! > > Bertand you are right. In the "view source" I can see the > namespace declaration. > > I'm feeling very stupid right now. s-: > > Tanks > > Marcel > > > -Oorspronkelijk bericht- > Van: Bertrand Delacretaz [mailto:[EMAIL PROTECTED] > Verzonden: dinsdag 3 januari 2006 12:47 > Aan: users@cocoon.apache.org > Onderwerp: Re: Problem writing generator > > Le 3 janv. 06, à 10:40, Marcel Rouwenhorst a écrit : > > > ...This example creates the following xml: > > > > > > ... > > How are you looking at this? I think your code is correct, so maybe > it's your view of the generated XML that is wrong? > > Using the "view source" function of a browser might not show you the > namespace declarations - saving the output with wget and > looking at the > saved file is more precise. > > -Bertrand > > > - > 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]
Re: 2.1.8 Build Failed. Cannot find file validate-build.xml.
Le 3 janv. 06, à 13:15, Russell Brown a écrit : That might be my problem:- $ md5sum cocoon-2.1.8-src.tar.gz 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz I tried another mirror and got $ md5sum cocoon-2.1.8-src.tar.gz 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz This time. Erm.. Is it me ? I am downloading the tar.gz as my office "security" forbids .zip files (I don't know why). You can find the md5sum at http://cocoon.apache.org/mirror.cgi as well, it's the same that I put in my previous message. Technically it is possible that files might be incorrect on mirrors, but weirdnesses in proxy/firewall handling are more likely IMHO. -Bertrand smime.p7s Description: S/MIME cryptographic signature
RE: 2.1.8 Build Failed. Cannot find file validate-build.xml.
That might be my problem:- $ md5sum cocoon-2.1.8-src.tar.gz 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz I tried another mirror and got $ md5sum cocoon-2.1.8-src.tar.gz 067382a26b3a2520e44ad8e36f9d15d1 *cocoon-2.1.8-src.tar.gz This time. Erm.. Is it me ? I am downloading the tar.gz as my office "security" forbids .zip files (I don't know why). Thanks Russell -Original Message- From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED] Sent: 03 January 2006 11:59 To: users@cocoon.apache.org Subject: Re: 2.1.8 Build Failed. Cannot find file validate-build.xml. Le 3 janv. 06, à 12:51, Russell Brown a écrit : > I have had a look at the build.xml and it simply includes a list > of other xxx-build.xml files from the tools/targets/ directory. I have > looked in that directory and there is no validate-build.xml. Also > there is not a webapp-build.xml, tools-build.xml nor upgrade build.xml... Something seems to be wrong with your download or the way it was extracted, here's what you should see: tar ztvf cocoon-2.1.8-src.tar.gz | grep build.xml tar: Record size = 16 blocks -rw-r--r-- / 3568 2005-11-17 09:19:03 cocoon-2.1.8/build.xml -rw-r--r-- / 862 2005-11-17 09:18:25 cocoon-2.1.8/src/blocks/axis/build.xml -rw-r--r-- / 1076 2005-11-17 09:19:00 cocoon-2.1.8/src/blocks/hsqldb/build.xml -rw-r--r-- / 3548 2005-11-17 09:18:42 cocoon-2.1.8/src/blocks/ojb/build.xml -rw-r--r-- / 2499 2005-11-17 09:18:56 cocoon-2.1.8/src/blocks/serializers/charsets/build.xml -rw-r--r-- / 2075 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/admin-build.xml -rw-r--r-- / 8961 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/compile-build.xml -rw-r--r-- / 3591 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/dist-build.xml -rw-r--r-- / 1137 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/docs-build.xml -rw-r--r-- / 3427 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/ide-build.xml -rw-r--r-- / 7654 2005-11-17 09:17:49 cocoon-2.1.8/tools/targets/init-build.xml -rw-r--r-- / 1462 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/instrumentation-build.xml -rw-r--r-- / 3074 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/samples-build.xml -rw-r--r-- / 3061 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/standalone-demo-build.xml -rw-r--r-- / 12824 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/test-build.xml -rw-r--r-- / 1524 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/tools-build.xml -rw-r--r-- / 11333 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/upgrade-build.xml -rw-r--r-- / 4651 2005-11-17 09:17:49 cocoon-2.1.8/tools/targets/validate-build.xml -rw-r--r-- / 6305 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/webapp-build.xml and if you want to check your downloaded file: $ md5sum cocoon-2.1.8-src.tar.gz 98ecb00c42ed41525cb6f098eacf76e5 cocoon-2.1.8-src.tar.gz -Bertrand The Information contained in this e-mail message is intended only for the individuals named above. If you are not the intended recipient, you should be aware that any dissemination, distribution, forwarding or other duplication of this communication is strictly prohibited. The views expressed in this e-mail are those of the individual author and not necessarily those of LINK Interchange Network Ltd. Prior to taking any action based upon this e-mail message you should seek appropriate confirmation of its authenticity. If you have received this e-mail in error, please notify the sender immediately. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem writing generator
Thanks Bertrand and Geert for answering! Bertand you are right. In the "view source" I can see the namespace declaration. I'm feeling very stupid right now. s-: Tanks Marcel -Oorspronkelijk bericht- Van: Bertrand Delacretaz [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 3 januari 2006 12:47 Aan: users@cocoon.apache.org Onderwerp: Re: Problem writing generator Le 3 janv. 06, à 10:40, Marcel Rouwenhorst a écrit : > ...This example creates the following xml: > > > ... How are you looking at this? I think your code is correct, so maybe it's your view of the generated XML that is wrong? Using the "view source" function of a browser might not show you the namespace declarations - saving the output with wget and looking at the saved file is more precise. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: from sumit sanwal==
Sumit wrote: How could I have my Cocoon app located in a directory other than $TOMCAT_HOME/webapps/cocoon/? It is related the tomcat context concept. A hint can be found here: http://wiki.apache.org/cocoon/BeginnerDefaultContext Maybe it does not fully answer your question, but hope this helps. Best Regards, Antonio Gallardo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Build 2.1.8 with Java 1.5
I had similar problems with building Cocoon 2.1.7 and 2.1.8 with Java 1.5 and running with Java 1.5. My recommendation is to build with and run with Java 1.4.2_10. Since I switched to Java 1.4.2_10 everything has worked. Gary T. Schultz IT Administrator Wisconsin Department of Commerce 608-266-1283 [EMAIL PROTECTED] -Original Message- From: Stefan Ivanov [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 03, 2006 3:43 AM To: users@cocoon.apache.org Subject: Build 2.1.8 with Java 1.5 Hi there I'm trying to build cocoon 2.1.8 with no success. I tried with 2.1.7 too. I allways have some failure. Here the message with the 2.1.8: ... cocoon-block-html-compile: Compiling 3 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\html\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\html-block.jar cocoon-block-jcr-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\jcr\dest cocoon-block-jcr-compile: Compiling 6 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\jcr\dest Copying 1 file to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoo n-2.1.8\blocks\jcr\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\jcr-block.jar cocoon-block-linkrewriter-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\linkrewriter\dest cocoon-block-linkrewriter-compile: Compiling 4 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\linkrewriter\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\linkrewriter-block.jar cocoon-block-lucene-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\lucene\dest cocoon-block-lucene-compile: Compiling 12 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\ build\cocoon-2.1.8\blocks\lucene\dest Copied 1 empty directory to 1 empty directory under D:\_dev\pfh\modules\pfh-cms- lenya\src\cocoon-2.1.8\build\cocoon-2.1.8\blocks\lucene\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\lucene-block.jar cocoon-block-naming-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\naming\dest cocoon-block-naming-compile: Compiling 3 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\naming\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\naming-block.jar cocoon-block-profiler-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\profiler\dest cocoon-block-profiler-compile: Compiling 9 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\profiler\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\profiler-block.jar cocoon-block-proxy-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\proxy\dest cocoon-block-proxy-compile: Compiling 4 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\proxy\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\proxy-block.jar cocoon-block-querybean-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\querybean\dest cocoon-block-querybean-compile: Compiling 5 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\querybean\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\querybean-block.jar cocoon-block-serializers-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\serializers\dest cocoon-block-serializers-compile: Compiling 19 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\ build\cocoon-2.1.8\blocks\serializers\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\serializers-block.jar cocoon-block-validation-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\validation\dest cocoon-block-validation-compile: Compiling 23 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\ build\cocoon-2.1.8\blocks\validation\dest Copying 1 file to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoo n-2.1.8\blocks\validation\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\validation-block.jar cocoon-block-xsltal-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\xsltal\dest cocoon-block-
Re: 2.1.8 Build Failed. Cannot find file validate-build.xml.
Le 3 janv. 06, à 12:51, Russell Brown a écrit : I have had a look at the build.xml and it simply includes a list of other xxx-build.xml files from the tools/targets/ directory. I have looked in that directory and there is no validate-build.xml. Also there is not a webapp-build.xml, tools-build.xml nor upgrade build.xml... Something seems to be wrong with your download or the way it was extracted, here's what you should see: tar ztvf cocoon-2.1.8-src.tar.gz | grep build.xml tar: Record size = 16 blocks -rw-r--r-- / 3568 2005-11-17 09:19:03 cocoon-2.1.8/build.xml -rw-r--r-- / 862 2005-11-17 09:18:25 cocoon-2.1.8/src/blocks/axis/build.xml -rw-r--r-- / 1076 2005-11-17 09:19:00 cocoon-2.1.8/src/blocks/hsqldb/build.xml -rw-r--r-- / 3548 2005-11-17 09:18:42 cocoon-2.1.8/src/blocks/ojb/build.xml -rw-r--r-- / 2499 2005-11-17 09:18:56 cocoon-2.1.8/src/blocks/serializers/charsets/build.xml -rw-r--r-- / 2075 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/admin-build.xml -rw-r--r-- / 8961 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/compile-build.xml -rw-r--r-- / 3591 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/dist-build.xml -rw-r--r-- / 1137 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/docs-build.xml -rw-r--r-- / 3427 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/ide-build.xml -rw-r--r-- / 7654 2005-11-17 09:17:49 cocoon-2.1.8/tools/targets/init-build.xml -rw-r--r-- / 1462 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/instrumentation-build.xml -rw-r--r-- / 3074 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/samples-build.xml -rw-r--r-- / 3061 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/standalone-demo-build.xml -rw-r--r-- / 12824 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/test-build.xml -rw-r--r-- / 1524 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/tools-build.xml -rw-r--r-- / 11333 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/upgrade-build.xml -rw-r--r-- / 4651 2005-11-17 09:17:49 cocoon-2.1.8/tools/targets/validate-build.xml -rw-r--r-- / 6305 2005-11-17 09:17:50 cocoon-2.1.8/tools/targets/webapp-build.xml and if you want to check your downloaded file: $ md5sum cocoon-2.1.8-src.tar.gz 98ecb00c42ed41525cb6f098eacf76e5 cocoon-2.1.8-src.tar.gz -Bertrand smime.p7s Description: S/MIME cryptographic signature
2.1.8 Build Failed. Cannot find file validate-build.xml.
Hi, I am trying to build and install Cocoon 2.1.8. I am on Windows XP running JDK. I have downloaded the 2.1.8 release and untarred it. I have typed "build.bat" at my shell prompt and I get the following error from ant BUILD FAILED M:\cocoon-2.1.8\build.xml:39: Cannot find tools/targets/validate-build.xml imported from M:\cocoon-2 .1.8\build.xml I have had a look at the build.xml and it simply includes a list of other xxx-build.xml files from the tools/targets/ directory. I have looked in that directory and there is no validate-build.xml. Also there is not a webapp-build.xml, tools-build.xml nor upgrade build.xml. I downloaded the latest source package just in case and the same issue persists. Where can I get the missing files from ? Should they be in the src package or should I delete the lines from the build.xml ? I am trying to build cocoon as the first step to installing and learning to use Apache Lenya. Many thanks in advance Russell Russell Brown Developer LINK Interchange Network Ltd Tel: 01423 356316 The Information contained in this e-mail message is intended only for the individuals named above. If you are not the intended recipient, you should be aware that any dissemination, distribution, forwarding or other duplication of this communication is strictly prohibited. The views expressed in this e-mail are those of the individual author and not necessarily those of LINK Interchange Network Ltd. Prior to taking any action based upon this e-mail message you should seek appropriate confirmation of its authenticity. If you have received this e-mail in error, please notify the sender immediately. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem writing generator
Le 3 janv. 06, à 10:40, Marcel Rouwenhorst a écrit : ...This example creates the following xml: ... How are you looking at this? I think your code is correct, so maybe it's your view of the generated XML that is wrong? Using the "view source" function of a browser might not show you the namespace declarations - saving the output with wget and looking at the saved file is more precise. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: Problem writing generator
What serializer are you using? Perhaps the problem is elsewhere. Your first code snippet looks okay
to me...
Cheers,
Geert
Marcel Rouwenhorst wrote:
Thanks Geert for answering!
I do use the startPrefixMapping and endPrefixMapping
This are the two source code examples I tried:
1 --
handler.startPrefixMapping("i18n", I18nTransformer.I18N_NAMESPACE_URI);
AttributesImpl attr = new AttributesImpl();
attr.addCDATAAttribute(I18nTransformer.I18N_NAMESPACE_URI, "key",
"i18n:" + "key", "some_key");
handler.startElement(null, "exception", "exception", null);
handler.startElement(I18nTransformer.I18N_NAMESPACE_URI, "text",
"i18n:text", attr);
handler.endElement(I18nTransformer.I18N_NAMESPACE_URI, "text",
"i18n:text");
handler.endElement(null, "exception", "exception");
handler.endPrefixMapping("i18n");
This example creates the following xml:
2-
If I change the following 2 lines
handler.startPrefixMapping("xmlns", I18nTransformer.I18N_NAMESPACE_URI);
attr.addCDATAAttribute(I18nTransformer.I18N_NAMESPACE_URI, "i18n",
"xmlns:i18n", I18nTransformer.I18N_NAMESPACE_URI);
This example creates the following xml:
http://apache.org/cocoon/i18n/2.1";
xmlns:i18n="http://apache.org/cocoon/i18n/2.1"/>
You can see that there are 2 i18n:text
xmlns:i18n="http://apache.org/cocoon/i18n/2.1";
I get an error "XML Parsing Error: duplicate attribute"
Thank you,
Marcel
-Oorspronkelijk bericht-
Van: Geert Josten [mailto:[EMAIL PROTECTED]
Verzonden: dinsdag 3 januari 2006 10:08
Aan: users@cocoon.apache.org
Onderwerp: Re: Problem writing generator
Are you using startPrefixMapping and endPrefixMapping to register the
i18n namespace?
Kind regards,
Geert
Marcel Rouwenhorst wrote:
Hi,
I have a problem writing a generator. I want to write a generator for
exception handling. It should work something like the exception
generator.
The generator should create an output that looks like this
(simplified):
http://apache.org/cocoon/i18n/2.1";>
test
I get everything right except I can't create
xmlns:i18n="http://apache.org/cocoon/i18n/2.1"; in the exception tag or
any other tag.
I use the org.xml.sax.ContentHandler to create the xml. In the same
way
as the exception generator does.
Help is appreciated
Marcel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [2.2] Problems with JMX Support and Tomcat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 2 Jan 2006, Sumit wrote: Date: Mon, 2 Jan 2006 21:15:32 +0530 From: Sumit <[EMAIL PROTECTED]> Reply-To: users@cocoon.apache.org, [EMAIL PROTECTED] To: users@cocoon.apache.org Subject: [2.2] Problems with JMX Support and Tomcat I'm trying to get the latest 2.2 running in a standard tomcat 5.5.12 With the default webapp, the following class can't be found: org.mortbay.log.LogFactory So it seems that the jetty-jmx-5.1.8.jar does not contain all required classes. Copying also jetty-5.1.8.jar into WEB-INF/lib of course solves this problem. Yes, the problem is known and JMX support is experimental and brand new. We are trying to solve this as soon as possible. Sorry for the inconvenience. - -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDulmSLNdJvZjjVZARAuecAJ97uTrBQ9mHkUQlS1XBdzheetaNGQCggAx6 KK1Ua5z0IhFiszziedKtOJw= =WB77 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Build 2.1.8 with Java 1.5
Hi there I'm trying to build cocoon 2.1.8 with no success. I tried with 2.1.7 too. I allways have some failure. Here the message with the 2.1.8: ... cocoon-block-html-compile: Compiling 3 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\html\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\html-block.jar cocoon-block-jcr-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\jcr\dest cocoon-block-jcr-compile: Compiling 6 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\jcr\dest Copying 1 file to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoo n-2.1.8\blocks\jcr\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\jcr-block.jar cocoon-block-linkrewriter-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\linkrewriter\dest cocoon-block-linkrewriter-compile: Compiling 4 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\linkrewriter\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\linkrewriter-block.jar cocoon-block-lucene-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\lucene\dest cocoon-block-lucene-compile: Compiling 12 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\ build\cocoon-2.1.8\blocks\lucene\dest Copied 1 empty directory to 1 empty directory under D:\_dev\pfh\modules\pfh-cms- lenya\src\cocoon-2.1.8\build\cocoon-2.1.8\blocks\lucene\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\lucene-block.jar cocoon-block-naming-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\naming\dest cocoon-block-naming-compile: Compiling 3 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\naming\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\naming-block.jar cocoon-block-profiler-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\profiler\dest cocoon-block-profiler-compile: Compiling 9 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\profiler\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\profiler-block.jar cocoon-block-proxy-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\proxy\dest cocoon-block-proxy-compile: Compiling 4 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\proxy\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\proxy-block.jar cocoon-block-querybean-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\querybean\dest cocoon-block-querybean-compile: Compiling 5 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b uild\cocoon-2.1.8\blocks\querybean\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\querybean-block.jar cocoon-block-serializers-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\serializers\dest cocoon-block-serializers-compile: Compiling 19 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\ build\cocoon-2.1.8\blocks\serializers\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\serializers-block.jar cocoon-block-validation-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\validation\dest cocoon-block-validation-compile: Compiling 23 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\ build\cocoon-2.1.8\blocks\validation\dest Copying 1 file to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoo n-2.1.8\blocks\validation\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\validation-block.jar cocoon-block-xsltal-prepare: Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1 .8\blocks\xsltal\dest cocoon-block-xsltal-compile: Copying 1 file to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoo n-2.1.8\blocks\xsltal\dest Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2. 1.8\blocks\xsltal-block.jar cocoon-block-forms-roles: Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\forms\ conf\forms-binding.xroles Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\forms\ conf\forms-cache.xroles Processing: D:\_dev\pfh\mod
RE: Problem writing generator
Thanks Geert for answering!
I do use the startPrefixMapping and endPrefixMapping
This are the two source code examples I tried:
1 --
handler.startPrefixMapping("i18n", I18nTransformer.I18N_NAMESPACE_URI);
AttributesImpl attr = new AttributesImpl();
attr.addCDATAAttribute(I18nTransformer.I18N_NAMESPACE_URI, "key",
"i18n:" + "key", "some_key");
handler.startElement(null, "exception", "exception", null);
handler.startElement(I18nTransformer.I18N_NAMESPACE_URI, "text",
"i18n:text", attr);
handler.endElement(I18nTransformer.I18N_NAMESPACE_URI, "text",
"i18n:text");
handler.endElement(null, "exception", "exception");
handler.endPrefixMapping("i18n");
This example creates the following xml:
2-
If I change the following 2 lines
handler.startPrefixMapping("xmlns", I18nTransformer.I18N_NAMESPACE_URI);
attr.addCDATAAttribute(I18nTransformer.I18N_NAMESPACE_URI, "i18n",
"xmlns:i18n", I18nTransformer.I18N_NAMESPACE_URI);
This example creates the following xml:
http://apache.org/cocoon/i18n/2.1";
xmlns:i18n="http://apache.org/cocoon/i18n/2.1"/>
You can see that there are 2 i18n:text
xmlns:i18n="http://apache.org/cocoon/i18n/2.1";
I get an error "XML Parsing Error: duplicate attribute"
Thank you,
Marcel
-Oorspronkelijk bericht-
Van: Geert Josten [mailto:[EMAIL PROTECTED]
Verzonden: dinsdag 3 januari 2006 10:08
Aan: users@cocoon.apache.org
Onderwerp: Re: Problem writing generator
Are you using startPrefixMapping and endPrefixMapping to register the
i18n namespace?
Kind regards,
Geert
Marcel Rouwenhorst wrote:
> Hi,
>
>
>
> I have a problem writing a generator. I want to write a generator for
> exception handling. It should work something like the exception
generator.
>
> The generator should create an output that looks like this
(simplified):
>
>
>
> http://apache.org/cocoon/i18n/2.1";>
>
> test
>
>
>
>
>
> I get everything right except I can't create
> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"; in the exception tag or
> any other tag.
>
>
>
> I use the org.xml.sax.ContentHandler to create the xml. In the same
way
> as the exception generator does.
>
>
>
> Help is appreciated
>
>
>
> Marcel
>
>
>
--
Drs. G.P.H. Josten
Consultant
Daidalos BV
Source of Innovation
Hoekeindsehof 1-4
2665 JZ Bleiswijk
Tel: +31 (0) 10 850 1200
Fax: +31 (0) 10 850 1199
www.daidalos.nl
De informatie - verzonden in of met dit emailbericht - is afkomstig van
Daidalos BV en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
onbedoeld hebt ontvangen, verzoeken
wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden
ontleend.
-
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]
Re: Problem writing generator
Are you using startPrefixMapping and endPrefixMapping to register the i18n namespace? Kind regards, Geert Marcel Rouwenhorst wrote: Hi, I have a problem writing a generator. I want to write a generator for exception handling. It should work something like the exception generator. The generator should create an output that looks like this (simplified): http://apache.org/cocoon/i18n/2.1";> test I get everything right except I can’t create xmlns:i18n="http://apache.org/cocoon/i18n/2.1” in the exception tag or any other tag. I use the org.xml.sax.ContentHandler to create the xml. In the same way as the exception generator does. Help is appreciated Marcel -- Drs. G.P.H. Josten Consultant Daidalos BV Source of Innovation Hoekeindsehof 1-4 2665 JZ Bleiswijk Tel: +31 (0) 10 850 1200 Fax: +31 (0) 10 850 1199 www.daidalos.nl De informatie - verzonden in of met dit emailbericht - is afkomstig van Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden ontleend. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem writing generator
Hi, I have a problem writing a generator. I want to write a generator for exception handling. It should work something like the exception generator. The generator should create an output that looks like this (simplified): test I get everything right except I can’t create xmlns:i18n="http://apache.org/cocoon/i18n/2.1” in the exception tag or any other tag. I use the org.xml.sax.ContentHandler to create the xml. In the same way as the exception generator does. Help is appreciated Marcel
