You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2011/03/16 20:42:29 UTC
[jira] Created: (WICKET-3540) Make AjaxLink's URL more configurable
Make AjaxLink's URL more configurable
-------------------------------------
Key: WICKET-3540
URL: https://issues.apache.org/jira/browse/WICKET-3540
Project: Wicket
Issue Type: Improvement
Components: wicket-core
Affects Versions: 1.5-RC2
Reporter: Martin Grigorov
Currently AjaxLink uses AjaxEventBehavior which exposes just its getAjaxCallDecorator() to the user.
It would be nice if there is a way to have access to the behavior callback url, e.g. to add some additional parameters, to set channel (wicket-ajax.js), etc.
As solution I suggest to add method "AjaxLink#newAjaxBehavior()" which by default will return current AjaxEventBehavior but if the user wants she may override it with custom one. This way wicket stateless ajax behavior (see jolira's google code project) can be used as well without the need to re-write (copy/paste) the whole class.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3540) Make AjaxLink's URL more
configurable
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009617#comment-13009617 ]
Martin Grigorov commented on WICKET-3540:
-----------------------------------------
The same problem is valid for AjaxFallbackLink and AjaxPagingNavigationIncrementLink.
> Make AjaxLink's URL more configurable
> -------------------------------------
>
> Key: WICKET-3540
> URL: https://issues.apache.org/jira/browse/WICKET-3540
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 1.5-RC2
> Reporter: Martin Grigorov
>
> Currently AjaxLink uses AjaxEventBehavior which exposes just its getAjaxCallDecorator() to the user.
> It would be nice if there is a way to have access to the behavior callback url, e.g. to add some additional parameters, to set channel (wicket-ajax.js), etc.
> As solution I suggest to add method "AjaxLink#newAjaxBehavior()" which by default will return current AjaxEventBehavior but if the user wants she may override it with custom one. This way wicket stateless ajax behavior (see jolira's google code project) can be used as well without the need to re-write (copy/paste) the whole class.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-3540) Make AjaxLink's URL more
configurable
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-3540.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC3
Assignee: Martin Grigorov
Improved with r1085907.
> Make AjaxLink's URL more configurable
> -------------------------------------
>
> Key: WICKET-3540
> URL: https://issues.apache.org/jira/browse/WICKET-3540
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 1.5-RC2
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 1.5-RC3
>
>
> Currently AjaxLink uses AjaxEventBehavior which exposes just its getAjaxCallDecorator() to the user.
> It would be nice if there is a way to have access to the behavior callback url, e.g. to add some additional parameters, to set channel (wicket-ajax.js), etc.
> As solution I suggest to add method "AjaxLink#newAjaxBehavior()" which by default will return current AjaxEventBehavior but if the user wants she may override it with custom one. This way wicket stateless ajax behavior (see jolira's google code project) can be used as well without the need to re-write (copy/paste) the whole class.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira