i use forms with DropDownChoices with fields which are IModel. When i test in
real life they work fine but when i test with FormTester field.getObject ()
only delivers null in onSubmit ()
Von meinem Samsung Galaxy Smartphone gesendet.
Hey guys,
I have some business logic where when the set method is called, it first
validates the value. In finding a “bad” value, it then throws a custom
validation exception. We use this pattern all over the place.
Is there some way to handle this situation so that it’s a valid wicket
Hi,
you actually need an AjaxFormSubmitBehavior to transfer all input values
to the server.
Note that AjaxFormValidatingBehavior attaches a AjaxFormSubmitBehavior
to *each* FormComponent in your form.
You could do something similar with a *single* AjaxFormSubmitBehavior
and event "focusout".
@Bas, I was originally adding it to the form (which is in a parent
component), but it just wasn’t working. I’m sure I’m missing something
about the nature of parent/child components.
@Sven Can you elaborate for me a little more (still a Wicket newb). Can I
use a AjaxEventBehavior with a Form?
Thanks, we'll try this!
Cheers
Lasse
2016-05-18 13:21 GMT+02:00 Bas Gooren :
> Hi all,
>
> We’ve encountered this issue, too; Simple fix is to touch the less file,
> even when a secondary file was the only change.
>
> The root cause is simple: wicket is not aware of any includes
Thanks Bas!
I see, this is new in Wicket 7.x (WICKET-5196).
We could delay the check for the parental form into #onConfigure().
IMHO a better solution would be to use a bubbling event instead (e.g.
"focusout") and attaching a single listener to the form (instead of
adding a behaviors to each
Uhh, that error message is right there on the AFVB’s onBind():
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/form/AjaxFormValidatingBehavior.java#L102
The problem is that the check for a parent form is happening in onBind(), so
when the behavior
Hi all,
We’ve encountered this issue, too; Simple fix is to touch the less file, even
when a secondary file was the only change.
The root cause is simple: wicket is not aware of any includes in the less file,
and as such only looks at the “parent” less file to see if it was changed. A
Hi Lasse,
I'll take a look in the coming days!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, May 18, 2016 at 11:43 AM, Lars Törner wrote:
> Hi Martin!
>
> We have now implemented this solution and we're using bootstrap-less -
>
Hi Martin!
We have now implemented this solution and we're using bootstrap-less -
thanks for that!
But we have a little problem...
The browser does not recognize when the css has changed, the cause seems to
be that the newly generated css is placed in a file with the same name as
before. The
Hi,
I cannot find that error message in Wicket's source.
Are you using org.apache.wicket.ajax.form.AjaxFormValidatingBehavior or
some subclass or alternative?
Have fun
Sven
On 18.05.2016 02:37, Lon Varscsak wrote:
Hey guys, I may be missing something here, but if I do:
TextField
11 matches
Mail list logo