On Fri, Aug 16, 2013 at 12:12 PM, Lucio Crusca wrote:
> > Everything is possible.
> > Just different tasks take different time to implement.
> > What did you try and what issues you faced so far ?
>
> Please see my previous message. To recap, I tried a mix you just told me
> it can't work: I adde
> Everything is possible.
> Just different tasks take different time to implement.
> What did you try and what issues you faced so far ?
Please see my previous message. To recap, I tried a mix you just told me
it can't work: I added the TextFields to the AjaxRequestTarget while
updating the bean i
Hi,
On Fri, Aug 16, 2013 at 10:58 AM, Lucio Crusca wrote:
> No replies... that must mean something... let's try rewording.
>
> I need to build several forms with:
>
> 1. Several text fields each, bound to several String properties of a
> single bean through a CompoundPropertyModel. This is a re
No replies... that must mean something... let's try rewording.
I need to build several forms with:
1. Several text fields each, bound to several String properties of a
single bean through a CompoundPropertyModel. This is a requirement unless
it renders all the rest impossible to implement.
2. On
> Take a look at how one drop-down updates the other via Ajax in the Wicket
> Examples at:
> http://www.wicket-library.com/wicket-examples/ajax/choice
>
> I suggest you do something similar instead of trying to re-implement part
> of the form processing in your code.
I've tried to follow that exam
> 1. where wicket is made aware of the fact that the target is actually the
> "models" dropdown and not something else in the form?
>
> I'm not sure I understand this question but I think the answer you're
> looking for is: because it has a behavior attached to a component to which
> you can gain a
I wrote:
> 2. the constructor 'new AjaxFormComponentUpdatingBehavior("onchange")'
> does not seem to exist in Wicket 6. Can I just use the no args
> constructor?
Please ignore this one, I was using
AjaxFormChoiceComponentUpdatingBehavior instead by mistake.
August 14, 2013 2:37 PM
To: users@wicket.apache.org
Subject: RE: Updating form fields on dropdown selection change
> Take a look at how one drop-down updates the other via Ajax in the
> Wicket Examples at:
> http://www.wicket-library.com/wicket-examples/ajax/choice
Thanks for the sugg
> Take a look at how one drop-down updates the other via Ajax in the Wicket
> Examples at:
> http://www.wicket-library.com/wicket-examples/ajax/choice
Thanks for the suggestion, that code looks good. However I don't
understand a number of things:
1. where wicket is made aware of the fact that the
Take a look at how one drop-down updates the other via Ajax in the Wicket
Examples at:
http://www.wicket-library.com/wicket-examples/ajax/choice
I suggest you do something similar instead of trying to re-implement part of
the form processing in your code.
Besides, what is going to happen when t
10 matches
Mail list logo