Hi Ernesto,
Yes, that is possible but it opens the route for lazy initialization
exceptions and such problems.
Really, why is it so hard to send multiple component values with an ajax
request? Maybe an AjaxFormComponentUpdating behavior which can update
multiple components?
On Mon, Feb 11,
create an smart LDM that goes to database only once and after that keeps
value?
Ηι,
AutoLabelMarker is a public static final class defined
inside org.apache.wicket.markup.html.form.AutoLabelResolver.
What I want to achieve is the following:
I have a form with five components, C1 through C5. C5 is disabled.
When one of C1, C2, C3, C4 change, the value for C5 is computed
Hi,
On Sun, Feb 10, 2019 at 10:29 PM mscoon wrote:
> Hi Martin,
>
> The form reloads the entity from the database (it uses a kind of loadable
> detachable model) at each ajax request, so it does not remember the values
> for the fields that have been modified in previous requests if we use
>
Hi Martin,
The form reloads the entity from the database (it uses a kind of loadable
detachable model) at each ajax request, so it does not remember the values
for the fields that have been modified in previous requests if we use
AjaxForm[Choice]ComponentUpdatingBehavior. This is why we use
Hi,
Why do you use AjaxFormSubmitBehavior ? It submits the whole form, i.e. all
its form components.
I think you want to use AjaxForm[Choice]ComponentUpdatingBehavior - it will
submit only the value of the modified field.
On Fri, Feb 8, 2019 at 2:57 PM mscoon wrote:
> Hi all,
>
> We have an
Hi all,
We have an outer form and an inner form. The inner form contains some form
components which all have an AjaxFormSubmitBehavior in order to update each
- other when the user changes one of them.
The actual submitting button is in the outer form.
When the AjaxFormSubmitBehavior runs and
