Hi Sven,
using clearInput() works.
I call it in onConfigure() of my DropDownChoice.
Ok, so far... but I'm still confused about the raw-input-handling.
Ususally, (and thats what I have in mind): components reflect the
current model objects state.
Whats the reason saving the raw-input and dete
Hi,
On Fri, Nov 20, 2015 at 3:22 PM, Patrick Davids <
patrick.dav...@nubologic.com> wrote:
> Hi Sven,
>
> using clearInput() works.
> I call it in onConfigure() of my DropDownChoice.
>
> Ok, so far... but I'm still confused about the raw-input-handling.
>
> Ususally, (and thats what I have in min
Hi Martin,
this is true for my DropDownChoice2.
But DropDownChoice1 does not get validated.
So, this could be the reason why it is not cleared.
Now... I'm getting more and more confused... *lol*
Page
Form A
DropDownChoice1 displaying selected 'Car 1'
Form
OK. I see what happens.
At
org.apache.wicket.markup.html.form.Form#onFormSubmitted(org.apache.wicket.markup.html.form.IFormSubmitter)
Wicket calls #inputChanged() for the root form, so this calls
#inputChanged() on *all* FormComponents (including nested ones).
My first reaction is: this is a bug!
> IMO the current behavior is wrong.
I don't see anything wrong with the current nested form handling. Care
to elaborate?
It's rather unusual to have to formComponents for the same model on a
single page.
IMHO Patrick shouldn't use nested forms in the first place, I consider
them an advanc
On Fri, Nov 20, 2015 at 4:37 PM, Sven Meier wrote:
> > IMO the current behavior is wrong.
>
> I don't see anything wrong with the current nested form handling. Care to
> elaborate?
>
The problem I see is that Wicket treats #inputChanged() differently than
all other Form processing methods (like
> When a nested form is submitted Wicket calls the processing methods
> only for the nested form.
> I don't see a reason why #inputChanged() should be an exception.
The outer form is not processed, because we don't want validation errors
to appear. #inputChanged() is called, so that on a possibl
Hi both,
ticket opened and quickstart attached.
https://issues.apache.org/jira/browse/WICKET-6041
Concerning reuseing components.
Yes, the clearInput() works, but the refreshed components, does not know
anything about another component, which changes something.
So, I got a dependency on behavio
Hi,
> In most cases it's not necessary to include a form in panels
In most case, I agree, but sometime, there is no other choice: wizard steps
for instance.
Best regards,
Sebastien
On Fri, Nov 20, 2015 at 5:02 PM, Sven Meier wrote:
> > When a nested form is submitted Wicket calls the process
On Fri, Nov 20, 2015 at 5:02 PM, Sven Meier wrote:
> > When a nested form is submitted Wicket calls the processing methods
> > only for the nested form.
> > I don't see a reason why #inputChanged() should be an exception.
>
> The outer form is not processed, because we don't want validation error
10 matches
Mail list logo
