-
1. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
ederfdo Nov 28, 2011 1:11 PM (in response to kwutzke)I don't know, but only removes the ColumnGroup and work -
2. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
mcmurdosound Nov 28, 2011 1:34 PM (in response to ederfdo)You could place the datascroller right after the table and not into the footer!
-
3. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
kwutzke Nov 28, 2011 8:20 PM (in response to ederfdo)@Eder: that doesn't work for me...
Karsten
-
4. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
kwutzke Nov 28, 2011 8:21 PM (in response to mcmurdosound)@Christian: I would like to keep the data scroller inside the table. That also has an aesthetic aspect, as the app's L&F is supposed to render a table footer all the time.
So, does this seem to be a bug?
Karsten
-
5. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
ederfdo Nov 28, 2011 8:31 PM (in response to kwutzke)Please show your datatable code
-
6. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
mcmurdosound Nov 29, 2011 1:47 AM (in response to ederfdo)@Karsten: If you don't find a useful workaround, just put an a4j:outputPanel arround the table and the datascroller. Rerender this one instead of the table (and its former inner datascroller).
-
7. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
kwutzke Nov 29, 2011 10:02 AM (in response to mcmurdosound)Note I'm not looking for a workaround but confirmation whether I basically use the components correctly and RF 4 has a bug or not. I might assume it to work, but if it *should* work, then I need to report a bug. Changing the code isn't really wanted. I wanted to ask in the forum beforehand.
Karsten
-
8. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
mcmurdosound Nov 29, 2011 10:08 AM (in response to kwutzke)1 of 1 people found this helpfulI'm not sure if it's really a bug. Might be just a limitation of the technology.
If you remove the conditionally rendered column:
<rich:column rowspan="#{companyFileGroup.numDocuments}" rendered="#{rowNbr eq 0}">
</rich:column>or just remove the "rendered" attribute, then it works and the datascroller uses the full size.
-
9. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
kwutzke Nov 30, 2011 8:33 PM (in response to mcmurdosound)Well, the problem is I can't get rid of the rich:column and I also can't omit the rendered attribute (it's necessary as a grouping element to generate a rowspan cell).
The problematic part in the generated HTML is:
{code}td class="rf-dt-ftr-c" colspan="3" scope="colgroup"><span class="rf-ds " ...{code}
Where you can see RF 4 somehow calculates a colspan of 3 instead of 4. This could be considered incorrect as the algorithm should determine 4 as the maximum number of columns from the JSF code (count the number of rich:columns?). I'm guessing RF 4 currently takes the last or previous row's HTML TDs of some sort.
I will file a bug for this so the RF guys can have a look at it.
Thanks
Karsten
-
10. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
mcmurdosound Dec 1, 2011 1:58 AM (in response to kwutzke)Hello again,
I've modified the rendered expression to handle another case:
rendered="#{empty rowNbr or rowNbr eq 0}"
this seems to work. Please try again.
Christian
-
11. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
kwutzke Dec 5, 2011 11:23 AM (in response to mcmurdosound)Indeed this works. However, I still consider this an issue with RF as rowNbr shouldn't be null anywhere during iteration (IMO). The bug is here: https://issues.jboss.org/browse/RF-11765
Thanks for helping!
Karsten
-
12. Re: Datatable footer doesn't use all columns when header specifies columnGroup?
bleathem Jan 24, 2012 5:07 PM (in response to kwutzke)I'm including my comment from the jira issue here, for the sake of completeness:
On analysing the provided code sample I've concluded that the current behaviour is correct. Consider the state while trying to count the number of columns while rendering the footer:
While rendering the footer, no row is active, hence rowNbr cannot return 0 (that would imply the 0th row is active). It counts the number of rendered columns to determine what to use for the colspan - if a column is not rendered, it should not be included in the count.
Hence the appropriate solution is indeed to alter the render logic of the column, so that it is counted while rendering the footer.