cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27785] - Form redisplays with validation errors after submit from <wd:action>
Date Thu, 18 Mar 2004 20:40:19 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27785>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27785

Form redisplays with validation errors after submit from <wd:action>





------- Additional Comments From ml@wrinkledog.com  2004-03-18 20:40 -------
I see this call chain:

Field.readFromRequest() =>
FIeld.getValue() =>
(super) AbstractWidget.validate() =>
(inherited from AbstractWidgetDefinition) FieldDefinition.validate()

This call chain is kicked off when the client invokes the continuation from sendPageAndWait().
<wd:submit validate="false"> just appears to work because its handleActivate() calls

Form.endProcessing(false), which tells the flow layer to just move on and not redisplay the
form.

The call to getValue() in Field.readFromRequest carries this comment in the source:

   // TODO: This cause validation to occur too early.

Mime
View raw message