cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <>
Subject Re: New error handling
Date Wed, 16 Apr 2003 13:07:43 GMT
Upayavira wrote:

>When the CLI crawls a site, using the default sitemap error handling, if there is a 
>page with a broken link, it will get stuck in an endless loop.
>When it requests the broken page, it gets back a 'sorry, cocoon can't find...', which

>has a reference to styles/main.css. It then tries styles/main.css, fails, looks for 
>styles/styles/main.css, etc, etc, etc.
>Is there a way that I can find out that a page has failed (either through an exception
>an error code) so that I can prevent the CLI from just accept the default page served


I would recommend:

1. Implement setStatus() in AbstractCommandLineEnvironment 
(implementation is empty right now)
2. Add getStatus() to the AbstractCommandLineEnvironment
3. Test getStatus() in the CLI crawling code.
4. Test how it works and fix the broken link :)

Hope this helps


>Regards, Upayavira

View raw message