Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 60606 invoked by uid 500); 2 Jul 2001 18:41:09 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Delivered-To: moderator for cocoon-users@xml.apache.org Received: (qmail 71622 invoked from network); 2 Jul 2001 11:31:25 -0000 Message-ID: <2099D12F8AC1D411BD7C00508B0BF5DD0E2CF9@startgwyex01.startamadeus.ie> From: Mercier Xavier To: "'cocoon-users@xml.apache.org'" Subject: Newbie Question: can't access some of Cocoon2's samples Date: Mon, 2 Jul 2001 12:28:27 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hi Cocooners, How's the craic? I'd been working so far with Cocoon1.8 but was very intrigued by Cocoon2 and decided eventually to give it a chance. Here is my environment: OS = Windows NT 4 Java = JDK 1.3 Application Server: BEA WebLogic 6 I built Cocoon2, then followed the installation instructions to the letter (http://xml.apache.org/cocoon2/install.html) and finally managed to access the Welcome Page after starting WebLogic. So far so good. Naturally, my first reaction is to try out the samples provided. Because I was essentially interested in XSP, I click on the Simple XSP Example link. No problemo. Actually, I can access everything related to Dynamic Content. When I try the simplest example though, named "Multimedia Hello World HTML" that transforms a simple XML page into an HTML page, I constantly obtain the following error: ---------------------------------------------------------------------------- ---------------------------------- Error 404--Not Found >From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1: 10.4.5 404 Not Found The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. ---------------------------------------------------------------------------- ---------------------------------- I tried to modify the sitemap.xmap file but with no success. I found nothing in the FAQ related to that. I'm surprised to see that Cocoon2 seems to work with more complicated examples. I'm baffled. Has anybody else ever experienced the same problem? If so, how did you solve it? Do you have suggestions? Please help me, and I'll drink a glass of Jameson tonight in your honor!! Thanks a bunch, Xavier --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: