Is there a way to create a StatelessForm that can *only* be submitted via
POST?

The current behavior of StatelessForm is to allow the form to be submitted
via GET even if the form's method is POST. I've provided two examples of
this behavior below (one each for Wicket 1.4 and 1.5). When you visit the
URIs below in a browser, you'll notice an error on the page that a
required field is missing. This indicates the form has been submitted via
GET (i.e. just by visiting the URI). So far I've found no way to prevent a
StatelessForm from being submitted via GET, but I'm not a Wicket power
user by any means so I'm hoping someone can help.

Wicket 1.4 example:
http://wicketstuff.org/wicket14/stateless/?wicket:bookmarkablePage=:org.apa
che.wicket.examples.stateless.StatelessPage&wicket:interface=:0:statelessfo
rm::IFormSubmitListener::


Wicket 1.5 example:
http://wicketstuff.org/wicket/stateless/foo?0-1.IFormSubmitListener-statele
ssform


I found and old bug WICKET-877 which supposedly addressed the issue, so I
created WICKET-4107 thinking that the current behavior of StatelessForm
may be a regression. However, I failed to adequately describe the issue on
the ticket, so I apologize for having to bring it up on both the list and
Jira. More detail can be found on WICKET-4107.

Thanks,
Chris Hansen
http://o.co


________________________________

CONFIDENTIALITY NOTICE: This message is intended only for the use and review of 
the individual or entity to which it is addressed and may contain information 
that is privileged and confidential. If the reader of this message is not the 
intended recipient, or the employee or agent responsible for delivering the 
message solely to the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please notify 
sender immediately by telephone or return email. Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to