> -----Original Message----- > From: Sylvain Wallez [mailto:[EMAIL PROTECTED] > Sent: maandag 17 november 2003 19:05 > To: [EMAIL PROTECTED] > Subject: Re: cvs commit: > cocoon-2.1/src/java/org/apache/cocoon/components/flow/javascri > pt/fom FOM_Cocoon.java > > > Unico Hommes wrote: > > <snip/> > > >>>Yeah, that sucks. > >>> > >>> > >>> > >>So, what about removing it and resolving the status-code? > This seems > >>way cleaner to me ;-) > >> > >> > > > >I just remembered that there is a setStatus() method on the > Environment > >interface too. If we use that, perhaps we can keep the > response.setStatus() method. Or do you see other objections > for this method? > > > > > > Well, ideally the flow stuff should not depend on the environment. > Formally, it just needs the object model and the redirector. >
What about defining the setStatus method on Response interface then? I really think we should be able to response.setStatus from the flow. In applications where you do advanced http handling I think it's desireable to keep all the http related processing in one place and not set the response headers in the flow and status code in the sitemap. Unico
