RE: upgrading to Cocoon2 and debugging
Now I know, I things have changed. My sitemap doesn't work... first XMLDBCollection goes wrong, but that one is deprecated. Then when I comment that one out I get a message: No default type exists for 'generate' at file:/D:/Tomcat4/webapps/cocoon/bugtrack/sitemap.xmap:95:-1 But I have a default, namely 'file' Regards Edgar -Oorspronkelijk bericht- Van: Graaf, Edgar de (fin) [mailto:[EMAIL PROTECTED]] Verzonden: vrijdag 17 mei 2002 9:07 Aan: '[EMAIL PROTECTED]' Onderwerp: RE: upgrading to Cocoon2 and debugging Thanks Konstantin! But what I don't understand is if this is faster and better, why is it commented out? I didn't do that Regards, Edgar -Oorspronkelijk bericht- Van: Konstantin Piroumian [mailto:[EMAIL PROTECTED]] Verzonden: donderdag 16 mei 2002 13:19 Aan: [EMAIL PROTECTED] Onderwerp: Re: upgrading to Cocoon2 and debugging From: Graaf, Edgar de (fin) [EMAIL PROTECTED] That I don't know because I never upgraded from C1. However when I adapt the sitemap while Cocoon is running it takes 10 seconds at least before cocoon is ready and the nullpointerexception dissapears. I can't remember that I've experienced any NPE with the TreeProcessor sitemap engine. Check if you are using it and not the compiled version (see 'sitemap' element in cocoon.xconf). Regards, Konstantin If there is nothing in the log or in your tomcat dos prompt do the following: call the url, wait 10 seconds (untill your processor calms down). Then reload -Oorspronkelijk bericht- Van: gorillacommunications [mailto:[EMAIL PROTECTED]] Verzonden: woensdag 15 mei 2002 22:54 Aan: [EMAIL PROTECTED] Onderwerp: upgrading to Cocoon2 and debugging Hi all. I am upgrading an application from Cocoon1 to Cocoon2 and am having some problems. I get the error Exception in creating Transform Handler: java.lang.NullPointerException. 1. I created a pipeline in sitemap.xmap, but are there any special things I must do to my XML and XSL files to upgrade? 2. How do I see meaningful debugging info? I looked in the archive and think I have the settings correct in web.xml and logkit.xconf, but I see no info in any of the logs for this application (other applications dump output to the logs). At least Cocoon1 would write a message to the console telling me what the parser choked on (I read in the archive that this message is caused by an error in the XSL). Thanks for any help. Leona Slepetis - 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] - 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] - 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] - 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] - 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]
Re: upgrading to Cocoon2 and debugging
Hello Edgar, Did you write map prefix, like map:generate ? Roman Graaf, Edgar de (fin) wrote: Now I know, I things have changed. My sitemap doesn't work... first XMLDBCollection goes wrong, but that one is deprecated. Then when I comment that one out I get a message: No default type exists for 'generate' at file:/D:/Tomcat4/webapps/cocoon/bugtrack/sitemap.xmap:95:-1 But I have a default, namely 'file' Regards Edgar -Oorspronkelijk bericht- Van: Graaf, Edgar de (fin) [mailto:[EMAIL PROTECTED]] Verzonden: vrijdag 17 mei 2002 9:07 Aan: '[EMAIL PROTECTED]' Onderwerp: RE: upgrading to Cocoon2 and debugging Thanks Konstantin! But what I don't understand is if this is faster and better, why is it commented out? I didn't do that Regards, Edgar -Oorspronkelijk bericht- Van: Konstantin Piroumian [mailto:[EMAIL PROTECTED]] Verzonden: donderdag 16 mei 2002 13:19 Aan: [EMAIL PROTECTED] Onderwerp: Re: upgrading to Cocoon2 and debugging From: Graaf, Edgar de (fin) [EMAIL PROTECTED] That I don't know because I never upgraded from C1. However when I adapt the sitemap while Cocoon is running it takes 10 seconds at least before cocoon is ready and the nullpointerexception dissapears. I can't remember that I've experienced any NPE with the TreeProcessor sitemap engine. Check if you are using it and not the compiled version (see 'sitemap' element in cocoon.xconf). Regards, Konstantin If there is nothing in the log or in your tomcat dos prompt do the following: call the url, wait 10 seconds (untill your processor calms down). Then reload -Oorspronkelijk bericht- Van: gorillacommunications [mailto:[EMAIL PROTECTED]] Verzonden: woensdag 15 mei 2002 22:54 Aan: [EMAIL PROTECTED] Onderwerp: upgrading to Cocoon2 and debugging Hi all. I am upgrading an application from Cocoon1 to Cocoon2 and am having some problems. I get the error Exception in creating Transform Handler: java.lang.NullPointerException. 1. I created a pipeline in sitemap.xmap, but are there any special things I must do to my XML and XSL files to upgrade? 2. How do I see meaningful debugging info? I looked in the archive and think I have the settings correct in web.xml and logkit.xconf, but I see no info in any of the logs for this application (other applications dump output to the logs). At least Cocoon1 would write a message to the console telling me what the parser choked on (I read in the archive that this message is caused by an error in the XSL). Thanks for any help. Leona Slepetis - 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] - 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] - 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] - 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] - 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] - 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]
RE: upgrading to Cocoon2 and debugging
Well I haven't changed that part of the sitemap. I left it like apache created it. Besides the compiled version works with the same file. Edgar ps map:generate is used... -Oorspronkelijk bericht- Van: KOZLOV Roman [mailto:[EMAIL PROTECTED]] Verzonden: vrijdag 17 mei 2002 12:06 Aan: [EMAIL PROTECTED] Onderwerp: Re: upgrading to Cocoon2 and debugging Hello Edgar, Did you write map prefix, like map:generate ? Roman Graaf, Edgar de (fin) wrote: Now I know, I things have changed. My sitemap doesn't work... first XMLDBCollection goes wrong, but that one is deprecated. Then when I comment that one out I get a message: No default type exists for 'generate' at file:/D:/Tomcat4/webapps/cocoon/bugtrack/sitemap.xmap:95:-1 But I have a default, namely 'file' Regards Edgar -Oorspronkelijk bericht- Van: Graaf, Edgar de (fin) [mailto:[EMAIL PROTECTED]] Verzonden: vrijdag 17 mei 2002 9:07 Aan: '[EMAIL PROTECTED]' Onderwerp: RE: upgrading to Cocoon2 and debugging Thanks Konstantin! But what I don't understand is if this is faster and better, why is it commented out? I didn't do that Regards, Edgar -Oorspronkelijk bericht- Van: Konstantin Piroumian [mailto:[EMAIL PROTECTED]] Verzonden: donderdag 16 mei 2002 13:19 Aan: [EMAIL PROTECTED] Onderwerp: Re: upgrading to Cocoon2 and debugging From: Graaf, Edgar de (fin) [EMAIL PROTECTED] That I don't know because I never upgraded from C1. However when I adapt the sitemap while Cocoon is running it takes 10 seconds at least before cocoon is ready and the nullpointerexception dissapears. I can't remember that I've experienced any NPE with the TreeProcessor sitemap engine. Check if you are using it and not the compiled version (see 'sitemap' element in cocoon.xconf). Regards, Konstantin If there is nothing in the log or in your tomcat dos prompt do the following: call the url, wait 10 seconds (untill your processor calms down). Then reload -Oorspronkelijk bericht- Van: gorillacommunications [mailto:[EMAIL PROTECTED]] Verzonden: woensdag 15 mei 2002 22:54 Aan: [EMAIL PROTECTED] Onderwerp: upgrading to Cocoon2 and debugging Hi all. I am upgrading an application from Cocoon1 to Cocoon2 and am having some problems. I get the error Exception in creating Transform Handler: java.lang.NullPointerException. 1. I created a pipeline in sitemap.xmap, but are there any special things I must do to my XML and XSL files to upgrade? 2. How do I see meaningful debugging info? I looked in the archive and think I have the settings correct in web.xml and logkit.xconf, but I see no info in any of the logs for this application (other applications dump output to the logs). At least Cocoon1 would write a message to the console telling me what the parser choked on (I read in the archive that this message is caused by an error in the XSL). Thanks for any help. Leona Slepetis - 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] - 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] - 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] - 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] - 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] - 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] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html
RE: upgrading to Cocoon2 and debugging
That I don't know because I never upgraded from C1. However when I adapt the sitemap while Cocoon is running it takes 10 seconds at least before cocoon is ready and the nullpointerexception dissapears. If there is nothing in the log or in your tomcat dos prompt do the following: call the url, wait 10 seconds (untill your processor calms down). Then reload -Oorspronkelijk bericht- Van: gorillacommunications [mailto:[EMAIL PROTECTED]] Verzonden: woensdag 15 mei 2002 22:54 Aan: [EMAIL PROTECTED] Onderwerp: upgrading to Cocoon2 and debugging Hi all. I am upgrading an application from Cocoon1 to Cocoon2 and am having some problems. I get the error Exception in creating Transform Handler: java.lang.NullPointerException. 1. I created a pipeline in sitemap.xmap, but are there any special things I must do to my XML and XSL files to upgrade? 2. How do I see meaningful debugging info? I looked in the archive and think I have the settings correct in web.xml and logkit.xconf, but I see no info in any of the logs for this application (other applications dump output to the logs). At least Cocoon1 would write a message to the console telling me what the parser choked on (I read in the archive that this message is caused by an error in the XSL). Thanks for any help. Leona Slepetis - 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] - 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]
Re: upgrading to Cocoon2 and debugging
From: Graaf, Edgar de (fin) [EMAIL PROTECTED] That I don't know because I never upgraded from C1. However when I adapt the sitemap while Cocoon is running it takes 10 seconds at least before cocoon is ready and the nullpointerexception dissapears. I can't remember that I've experienced any NPE with the TreeProcessor sitemap engine. Check if you are using it and not the compiled version (see 'sitemap' element in cocoon.xconf). Regards, Konstantin If there is nothing in the log or in your tomcat dos prompt do the following: call the url, wait 10 seconds (untill your processor calms down). Then reload -Oorspronkelijk bericht- Van: gorillacommunications [mailto:[EMAIL PROTECTED]] Verzonden: woensdag 15 mei 2002 22:54 Aan: [EMAIL PROTECTED] Onderwerp: upgrading to Cocoon2 and debugging Hi all. I am upgrading an application from Cocoon1 to Cocoon2 and am having some problems. I get the error Exception in creating Transform Handler: java.lang.NullPointerException. 1. I created a pipeline in sitemap.xmap, but are there any special things I must do to my XML and XSL files to upgrade? 2. How do I see meaningful debugging info? I looked in the archive and think I have the settings correct in web.xml and logkit.xconf, but I see no info in any of the logs for this application (other applications dump output to the logs). At least Cocoon1 would write a message to the console telling me what the parser choked on (I read in the archive that this message is caused by an error in the XSL). Thanks for any help. Leona Slepetis - 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] - 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] - 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]
RE: upgrading to Cocoon2 and debugging
From: gorillacommunications [mailto:[EMAIL PROTECTED]] Hi all. I am upgrading an application from Cocoon1 to Cocoon2 and am having some problems. I get the error Exception in creating Transform Handler: java.lang.NullPointerException. Usually this means you have an error in the XSLT. See logs. 1. I created a pipeline in sitemap.xmap, but are there any special things I must do to my XML and XSL files to upgrade? 2. How do I see meaningful debugging info? I looked in the archive and think I have the settings correct in web.xml and logkit.xconf, but I see no info in any of the logs for this application (other applications dump output to the logs). At least Cocoon1 would write a message to the console telling me what the parser choked on (I read in the archive that this message is caused by an error in the XSL). Log files location is WEB-INF/logs, as Artur said. Vadim Thanks for any help. Leona Slepetis - 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]
RE: upgrading to Cocoon2 and debugging
Porting from Cocoon1 to Cocoon2 is like converting a gorilla to a submarine. If your project is small than I would read up on Cocoon2, rethink your approach and start from scratch, otherwise read on. -Original Message- From: gorillacommunications [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 4:54 PM To: [EMAIL PROTECTED] Subject: upgrading to Cocoon2 and debugging Hi all. I am upgrading an application from Cocoon1 to Cocoon2 and am having some problems. I get the error Exception in creating Transform Handler: java.lang.NullPointerException. This is not enough info 1. I created a pipeline in sitemap.xmap, but are there any special things I must do to my XML and XSL files to upgrade? There a quite a few change you have to do to XMLs. tag libs request, response, etc. are now xsp-request, xsp-response, etc. Also their namespace uris have changed so now you must have: xsp:page language=java xmlns:xsp-request=http://apache.org/xsp/request/2.0; and same for response, etc. If you used xspCurrentNode and its friends than you have to rewrite your XMLs to use SAX contentHandler instead. The fp taglib is not in C2, other taglibs have changed too. If your XMLs did redirection or changed stylesheets on the fly than you might need to write some Actions. 2. How do I see meaningful debugging info? I looked in the archive and think I have the settings correct in web.xml and logkit.xconf, but I see no info in any of the logs for this application (other applications dump output to the logs). At least Cocoon1 would write a message to the console telling me what the parser choked on (I read in the archive that this message is caused by an error in the XSL). there are sitemap.log error.log core.log and access.log probably in your deployed apps WEB-INF/logs. Look there. Artur... - 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]
