[WICKET-5884] Let Links, Buttons and Forms send Click and Submit Events

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Later
• Affects Version/s: 6.20.0, 7.0.0
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Tim Feurich
• Created: 16/Apr/15 15:38
• Updated: 04/May/15 19:17
• Resolved: 04/May/15 19:17

Description

Links, Buttons

Having the Link/Button components send click events to child IEventSinks  would allow decoupling their behavior into Behaviors  for reuse.
This would also make their anonymous subclassing optional.

add(new Link<>("logout")
	.add(new LogoutClickBehavior())
	.add(new ClickLogger("authentication")));

Sending the events to the children probably would suffice, as a custom behavior could easily reroute the events to other destinations.

add(new Link<>("logout").add(EventPropagator.SESSION));

Forms

Form onSubmit events would allow Behaviors to contribute to the submission without forcing users to subclass forms for any number of tasks.

MailingStatelessContactForm.class
DatabasePersistedContactForm.class
XSDValidatingJAXBMarshallingAgainstXMLRantingContactForm.class

The decoupled behavior is quite a bit more flexible and reuseable compared to individual classes for every combination of usecases.

add(new ContactForm<>(id, model)
	//decoupled behavior, that can be made to work for any form
	.add(new FormMailBehavior("[e-mail]"))
	.add(new DevFormDumper()));

Using listeners instead of the IEvent mechanism might be a viable alternative with a typesafty-flexibility tradeoff.
Although there might be a naming conflict with IFormSubmitListener, which seems quite different in nature.

Issue Links

• links to: Discussion at dev@