A more general purpose way to trigger an AJAX zone update is to
include an empty t:form (with style="display:none") and the do $
('myFormId').submit() from any JavaScript method you'd create that
needs to trigger an event. Somewhat of a hack, but I've been using
this a lot for many different
Hello Kalle,
Kalle Korhonen schrieb:
I don't see it as a workaround considering that you'd do exactly the
same if it was a regular form.
I do not fully agree here. I use the beaneditform to get rid of
t:textfield and t:label components. I don't want to fall back on normal
form writing. To rec
The setter exists and is public. I think the point of the problem is that I
access to a related POJO. 'Incidencia' is the class being showed at the bean
display and I'm trying to show a foreign key, which is the id of an object with
the relation ("Incidencia <-> @ManyToOne <-> Empleado) .
>
> Have I overlooked something? Is there some other way to accomplish
> this? With the current implementation it seems like my only real
> option is to use:
Have you thought about creating a custom errors component that does a better
job at displaying equal error-messages for different componen
