Yes, the problem doesn't seem to be a temporary one. I recently got a mail from Carsten Ziegeler and he told me that the CVS version worked fine for him, but he didn't know where my error came from. A few months ago it still worked..
I think we're doing something wrong, but i don't know what. Lars On Sun, 23 Mar 2003, Michael Riedel wrote: > > today i wanted to build and install the newest > > Cocoon 2.1 dev from CVS. I did it like always (build war), > > but this time the compiled Cocoon didn't work. > > I had the same problem, even though a few days already passed. The > Cocoon-Servlet works, but only deliveres the error-message you mentioned: > > > Request Processing Failed > > > > Message: Cocoon engine failed in process the request > > > > Description: The processing engine failed to process > > the request. This could be due to lack of matching or > > bugs in the pipeline engine. > > > > Sender: org.apache.cocoon.servlet.CocoonServlet > > > > Source: Cocoon Servlet > > > > Request URI > > request-uri > > /cocoon/ > > > > Apache Cocoon 2.1-dev > > It is displayed, whenever you request the welcome-page, or any other page > which should normally apear. If a resource which is not specified in the > sitemap is requested, another error-message apears. But since it states > > Also when I build I get the following error at the end: > > validate-xdocs: > Conducting validation of core XML documentation. > Validating all **/book.xml instances using RELAX NG ... > Fatal error: exception "java.net.MalformedURLException" thrown: no > protocol: dtd/book-cocoon-v10.dtd > > BUILD FAILED > > file:///G:/Dokumente%20und%20Einstellungen/Michael/Eigene%20Dateien/WebSites > /cocoon-2.1/build.xml:835: Validation failed, messages should have been > provided. > > ... but anything else seams to be built correctly. Also when I set > validate.xdocs=false in local.build.properties, the error does not occur, > and the build is successfull. So I don't think, the problem lies here. > > However, I have no clue what could still be wrong. None of the hints from > the mail-list worked for me so far. And I've also tried several CVS updates > by now, so it's not a temporar problem. > > -- Michael Riedel > > > > --------------------------------------------------------------------- > 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]
