-
1. Re: Tomahawk data table header a4j:commandLink - ajaxSingle=
ilya_shaikovsky Sep 22, 2008 4:59 AM (in response to roku)seems it's a problem while using tomahawk dataTable. please try to change it to rich:dataTable.
-
2. Re: Tomahawk data table header a4j:commandLink - ajaxSingle=
roku Sep 22, 2008 5:01 AM (in response to roku)"ilya_shaikovsky" wrote:
seems it's a problem while using tomahawk dataTable. please try to change it to rich:dataTable.
No, that is no option for me. I have to use t:datatable. -
3. Re: Tomahawk data table header a4j:commandLink - ajaxSingle=
roku Sep 22, 2008 5:02 AM (in response to roku)As soon as I place the a4j:commandLink outside the header facet, everything works fine.
-
4. Re: Tomahawk data table header a4j:commandLink - ajaxSingle=
ilya_shaikovsky Sep 22, 2008 6:47 AM (in response to roku)our dataTable has specific code in order to support regions inside table (ajax single is analogous to region around the component). So there is no problems with our action components but the problem inside t: table.
B.t.w. why you can't use our dataTable. Just describe any problems and I think we'll solve them ;) -
5. Re: Tomahawk data table header a4j:commandLink - ajaxSingle=
roku Sep 22, 2008 11:10 AM (in response to roku)I do not think that is has directly to do with t:datatable. I debugged through a4j, myfaces and tomhawk sources and it seems that processDecodes is doing different things depending on if the a4j:commandLink is inside a facet or not. There is a method somewhere called invokeOnComponent which does not find the correct children inside the datatable. I didn't find a solid peace of offending code yet, but maybe later.
Why I can not use rich table? Because our app is grown over years using myfaces and now we smoothly integrate some a4j features. Replacing all t:datatable with rich table would cause too much effort, which i'm not allowed to spent.