Nikolas List wrote: > Hi, > > I think I found the reason for the described problem - although no solution. > > Is it correct, that the "miracle" of super call is done in > ServletServiceContext.PathDispatcher.forward(..)? > Yes, it's correct. > If yes, the problem is, that the method call > > ServletServiceContext.this.servlet.service(request, wrappedResponse); > > (line 469 of ServletServiceContext.java) throws a > ResourceNotFoundException instead of response with error code 404. The > execution therefore continues in the finally block (line 484), never > calling the super servlet, as the status code of the response is never > checked. > > 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. I cannot check my fixes right now as I don't have an access to my Git repository where all this work was done. -- Grzegorz Kossakowski --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
