Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
vgritsenko2004/05/28 05:20:20
Modified:
src/blocks/forms/java/org/apache/cocoon/forms/flow/javascript
Form.js
src/java/org/apache/cocoon/components/flow/javascript/fom
Vadim Gritsenko wrote:
vgritsenko2004/05/28 05:20:20
Modified:
src/blocks/forms/java/org/apache/cocoon/forms/flow/javascript
Form.js
src/java/org/apache/cocoon/components/flow/javascript/fom
FOM_Cocoon.java
-Original Message-
From: Sylvain Wallez [mailto:[EMAIL PROTECTED]
Sent: maandag 17 november 2003 17:08
To: [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
unico 2003/11/14 10:58:18
Modified:
src/java/org/apache/cocoon/components/flow/javascript/fom
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()
-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,