[
https://issues.apache.org/jira/browse/WICKET-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-5299.
-------------------------------------
Resolution: Later
There is no much interest in this functionality at the moment.
Closing as "Later".
> Extract the main logic for Wicket Ajax functionality in a replaceable strategy
> ------------------------------------------------------------------------------
>
> Key: WICKET-5299
> URL: https://issues.apache.org/jira/browse/WICKET-5299
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 7.0.0-M1
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
>
> As suggested by Sven in http://markmail.org/message/cuymwe4turbo2yrx we can
> extract the code for Wicket Ajax functionality out of the base behaviors into
> strategy classes.
> This will allow replacing the logic per application.
> As a proof of concept the current code can be extracted in
> Wicket6AjaxStrategy and a new way based on data- attributes
> (http://markmail.org/message/kb7zzkwzwmnx7jd4) can be done in
> Wicket7AjaxStrategy (the class name may be changed/improved).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
