Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 80359 invoked from network); 28 Nov 2008 19:40:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Nov 2008 19:40:03 -0000 Received: (qmail 74979 invoked by uid 500); 28 Nov 2008 19:40:08 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 74918 invoked by uid 500); 28 Nov 2008 19:40:08 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 74907 invoked by uid 99); 28 Nov 2008 19:40:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2008 11:40:08 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [85.214.32.49] (HELO tabor.metromorph.de) (85.214.32.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2008 19:38:40 +0000 Received: from i53877c58.versanet.de ([83.135.124.88] helo=[192.168.0.6]) by tabor.metromorph.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1L69Ba-00064S-6a for users@cocoon.apache.org; Fri, 28 Nov 2008 20:39:30 +0100 Message-ID: <493048EB.5030205@metromorph.de> Date: Fri, 28 Nov 2008 20:39:23 +0100 From: Nikolas List User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: [C2.2, SSF] super connection doesn't work?? References: <49256830.4030000@metromorph.de> <492F99EE.7060709@metromorph.de> <492FE2EE.6040001@tuffmail.com> In-Reply-To: <492FE2EE.6040001@tuffmail.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, thanks for your help. Grzegorz Kossakowski schrieb: > Nikolas List wrote: [...] >> The old (2.2.0-RC2) version of ServletServiceContext did directly catch >> this Exception and did trigger a super call, as either an exception or >> status code < 200 or >= 400 is considered. >> > The old behaviour was wrong. >> Is this behaviour due to a misconfiguration of mine or is it a bug? >> > > I didn't think that this might be a reason. > Actually, I've been having similiar problems last summer and I applied > some fixes to Cocoon core so ResourceNotFound exceptions are not > propagated but 404 code is being returned instead. > > Are you using Cocoon core compiled from trunk of released version? If > it's a Cocoon trunk then it's very likely that I've missed something. No. I'm using the released versions from the maven repositories. (cocoon-core 2.2.0 and servlet-service-impl 1.0.0) After your mail I did try with cocoon-core 2.2.0 and servlet-service-impl 1.0.0 from http://http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2 Both don't work. The sources from trunk (rev 720182) provide the packages cocoon-core 2.2.1-SNAPSHOT and servlet-service-components 1.1.0-SNAPSHOT? I tried installing them as well and did adapt my poms, but the application fails to start with various java.lang.AbstractMethodError from rcl springreloader. What is the recommended way to use the packages from trunk in an existing application? Regards Niko > > I cannot check my fixes right now as I don't have an access to my Git > repository where all this work was done. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org