I don't think HTML forms can be nested.  This will hinder re-use of components that contain their own forms.  My solution is to build components with their own submit buttons with behavior built in, but which rely on being placed inside a form that covers the page as a whole.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nino Wael
Sent: Friday, June 23, 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 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 handles what is next and previous page.

 

So I wanted to hear what you have to say about this approach?

 

Some of the pros are:

 

Don’t have to worry about placing the component tags within a form since they bring their own.

 

Might have some advantage in case of sub updating the page(ajax?)?

 

 

Cons:

 

How does this affect updating the model of separate forms when one forms submit button are clicked.

 

Not sure how multiple forms perform versus single form.

 

 

 

 

Regards Nino

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to