Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 25841 invoked by uid 500); 30 May 2002 21:02:43 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 25830 invoked from network); 30 May 2002 21:02:43 -0000 Message-ID: <012e01c2081c$e7a0d960$cd340a3e@PC103> From: "Nicola Ken Barozzi" To: References: <3CF685F8.2020308@yahoo.de> Subject: Re: C2 on Websphere 3.5: IllegalStateException Date: Thu, 30 May 2002 22:59:34 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N From: "J.Pietschmann" > Hello, > finally I managed to get Cocoon 2.0.2 running on Websphere 3.5. > However, I keep getting IllegalStateExceptions, in particular > if a ressource is missing because of this code in > CocoonServlet.java:1019 ff: > res.sendError(res.SC_NOT_FOUND); > > SimpleNotifyingBean n = new SimpleNotifyingBean(this); > n.setType("resource-not-found"); > ... > // send the notification but don't include it in the output stream > // as the status SC_NOT_FOUND is enough > res.setContentType(Notifier.notify(n, (OutputStream)null)); > > Apparently Tomcat tolerates the setContentType() after a > sendError(), Websphere 3.5 has already it's response committed > at this point and throws the IllegalStateException. > > I'm not an expert in servlet programming, nevertheless the code > seems to be a bit odd to me. Is there a specific reason for > setting the content type after the sendError()? I'd send the > error after having set the content type... Yes, Houston, we have a problem. I think I wrote that comment more than a year ago :-| ... it's time I take a deeper look into it. It should throw a RNF exception, not get there... Anyway, the senderror part is wrong as you pointed out :-/ -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org