Forms in my components are not nested...
-Oprindelig meddelelse-
Fra: [EMAIL PROTECTED] på vegne af Frank Silbermann
Sendt: fr 23-06-2006 17:33
Til: wicket-user@lists.sourceforge.net
Cc:
Emne: Re: [Wicket-user] Multipleforms good idea
oh, and a form part like this:
private static final class TextFieldDefinitionEditor extends Panel
implements IFormEditor {
public TextFieldDefinitionEditor(String id, IModel
fieldDefinitionModel) {
super(id, new
CompoundPropertyModel(fieldDefiniti
Looks like this:
/**
* Parts of form.
*/
private static interface IFormEditor {
/** called by parent form on submitting. */
void onSubmit();
}
and the actual form:
protected void onSubmit() {
...
visitChildren(IFor
2006 2:48 AM
> To: wicket-user@lists.sourceforge.net
> Subject: [Wicket-user] Multipleforms good idea?
>
>
>
>
>
> Hi
>
>
>
> I've been creating some different components with wicket, so that I can
> reuse them. On some of my pages there is stuff which does
EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nino
WaelSent: Friday, June 23, 2006 2:48 AMTo:
wicket-user@lists.sourceforge.netSubject: [Wicket-user] Multipleforms
good idea?
Hi
I’ve been creating some different
components with wicket, so that I can reuse them. On some of my
The problem with using multiple forms is that only the data of one
form is submitted. So if your user has entered data in 2-3 forms, only
the form that is submitted retains its data.
So what we typically do is have one form on a page, and create panels
that contain form components, and add those t
Hi
I’ve been creating some different components
with wicket, so that I can reuse them. On some of my pages there is stuff which
does not encourage reuse. All my components have their own form, none of them
have regular submit buttons. This is handled in another component, which also
ha
