Konstantin Piroumian wrote: <snip/>
>>Just to know : what are these logs that you like so much ? Is >>there any other useful information that could be logged ? >> > >sitemap.log was the best one that gave me the correct error. Compiled >sitemap simply stated that 'No pipeline matched the request' with a >ResourceNotFoundException, while the real error was related to not >well-formed xml file and because of a wrong path to the error2html >stylesheet the original error was lost somewhere. > >It is quite hard to determine which pipeline was matched for the current >request, especially, when there are mounted/mounted sitemaps (see /sameples >for example). It would be fine (if it's possible) to have some information, >maybe only on exception cases, which pipeline and which sitemap caused that >exception. > I see. This can easily go into PipelineNode.invoke(). >I am now +100 for moving to TreeProcessor. Are there any issues that prevent >us to do it? > Not that I'm aware of (Torsten, Jeremy ?). So this is finally done : *TreeProcessor is the default sitemap engine* ! Enjoy ! Sylvain -- Sylvain Wallez Anyware Technologies Apache Cocoon http://www.anyware-tech.com mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
