[ 
https://issues.apache.org/jira/browse/WICKET-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036791#comment-16036791
 ] 

Kamil edited comment on WICKET-6392 at 6/5/17 10:37 AM:
--------------------------------------------------------

I already tried `markRendered` and it doesn't change anything - Validation 
Errors stays the same. Should I open another issue?

And about API change - what do you think about:
{code}
Form#clearValidationErrors();
{code}
?
Isn't it more obious than
{code}
new FeedbackCollector(form).collect().stream().forEach(fm -> fm.markRendered());
{code}
?


was (Author: eximius):
I already tried `markRendered` and it doesn't change anything - Validation 
Errors stays the same. Should I open another bug?

And about API change - what do you think about:
{code}
Form#clearValidationErrors();
{code}
?
Isn't it more obious than
{code}
new FeedbackCollector(form).collect().stream().forEach(fm -> fm.markRendered());
{code}
?

> Can not change Model when form has Validation Errors
> ----------------------------------------------------
>
>                 Key: WICKET-6392
>                 URL: https://issues.apache.org/jira/browse/WICKET-6392
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 8.0.0-M6
>            Reporter: Kamil
>
> I have a Modal with Form and Submit button (it is used for creating new 
> users).
> Form has several text fields bound to CompoundPropertyModel.
> Everytime I open the Modal, I set  the ModelObject as new User();
> It works fine (fields "see" new model if I cancel the window or if I sumbit 
> it without erors).
> If Form has validation errors, even if i set compoundModel.setObject(new 
> User()); fields have old value and validation erros are present.
> I found 
> [workaround|https://stackoverflow.com/questions/8879775/apache-wicket-how-to-update-model-after-validation-error]
>  but I believe it should be possible with Wicket without "workarounds"



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to