Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Subject: Re: [lazy vote] cforms request processing
From: Jason Johnston <jason.johnston@Intrado.com>
To: dev@cocoon.apache.org
In-Reply-To: <20041102205550.GE21226@localhost>
References: <20041101144706.GM26283@localhost>
	 <32899.80.219.8.172.1099354401.squirrel@80.219.8.172>
	 <20041102050841.GD21226@localhost>
	 <1099424028.4236.27.camel@jjohnston.lgmt.trdo>
	 <20041102205550.GE21226@localhost>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1099436028.12696.9.camel@jjohnston.lgmt.trdo>
Mime-Version: 1.0
Date: Tue, 02 Nov 2004 15:53:48 -0700

On Tue, 2004-11-02 at 13:55, Tim Larson wrote:
> 
> We would still perform validation.  The only thing we would not do
> is automatically reset a widget's value to null when its request
> parameter is missing.  Because we would still validate the widget,
> "required" widgets would still catch empty values like they do now.

Thanks for the clarification.  I was under the impression that the main
use-case for this new behavior was to be able to have a single form
split up across multiple views (multi-page forms) and not have a single
view fail validation if there is a required field not present in that
view (as is currently the case).  I can infer from your answer that this
is not the use-case you're tackling with this change.

Thanks again
--Jason