[
https://issues.apache.org/jira/browse/TOMAHAWK-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907509#action_12907509
]
Leonardo Uribe commented on TOMAHAWK-1548:
------------------------------------------
Yes, I think it is worth to dedicate some time to enhance compatibility of
tomahawk with ajax, and doing this we can find bugs on myfaces core as well.
> Allow t:dataScroller to be Ajaxified using f:ajax
> -------------------------------------------------
>
> Key: TOMAHAWK-1548
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1548
> Project: MyFaces Tomahawk
> Issue Type: Improvement
> Components: Data Scroller
> Affects Versions: 1.1.9
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 1.1.10-SNAPSHOT
>
>
> After thinking a lot about it, to make it possible we need to do some things:
> - If no facet or paginator is rendered, render a <div> and the id, so when
> ajax occur it could be replaced.
> - If a facet or paginator is rendered, if an id is set render it.
> - Add "click", "dblclick" and "action" client events and copy them for all
> facets and paginator links.
> - Add "action" as default event name.
> In this way, we can add f:ajax tag inside t:dataScroller to tell when a link
> is click, which elements should be updated (usually the related dataTable).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
