[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Nick Belaevski resolved RF-8469. -------------------------------- Resolution: Cannot Reproduce Bug Assignee: Nick Belaevski -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Leonid Sokolin updated RF-8469: ------------------------------- Attachment: piQueryToolOutputPR.xhtml Nick, Please see attached the file I use. I also attached the section from faces-config.xml, which is supporting this page. <managed-bean> <managed-bean-name>piQueryToolOutputBeanPR</managed-bean-name> <managed-bean-class> com.nb.pi.processor.beans.QueryToolOutputBean </managed-bean-class> <managed-bean-scope>request</managed-bean-scope> <managed-property> <property-name>statOutDataV</property-name> <value>#{piPerformanceReturnsBean.allRetData}</value> </managed-property> <managed-property> <property-name>outputIndex</property-name> <value>#{param.index}</value> </managed-property> </managed-bean> I would be curious to have your feedback. We need to decide whether we could use rich:dataTable to do the sorting (preferred solution) or I should look for the alternative. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Nick Belaevski commented on RF-8469: ------------------------------------ Leonid, Can you please attach bean code also? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Leonid Sokolin updated RF-8469: ------------------------------- Attachment: StatisticsOutputData.java Data for the output page -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Nick Belaevski commented on RF-8469: ------------------------------------ P.S. I haven't yet tried to resolve javax.servlet.jsp.JspTagException: FOREACH_BAD_ITEMS issue, can you please try the workaround described and let me know if the problem still exists? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Leonid Sokolin updated RF-8469: ------------------------------- Attachment: StatisticsValues.java Example of StatisticValues class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Nick Belaevski commented on RF-8469: ------------------------------------ Leonid, Can you please clarify on the version - is it 3.3.2.CR1, 3.3.2.SR1 or 3.3.3.CR1? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Nick Belaevski commented on RF-8469: ------------------------------------ "Nick, I looked to your suggestion and am a bit confused. You say: Unfortunately, support for "rowKeyVar" in sorting/filtering expressions is not implemented. I've created task to describe this in docs. You can use the following workaround (requires that StatisticsValues class has some kind of ID): 1) make prodBenchNames property a dictionary mapping id to StatisticsValues#getProduct() object 2) Rewrite sort expression as #{piQueryToolOutputBeanPR.statOutData.prodBenchNames[curPortBench.id]} But prodBenchNames is a vector and hence can't be addressed via the key. That's why I tried to use rowKeyVar as an iterator. You can't know the index value in StatisticValues class, because the only class that knows about prodBenchNames is StatisticOutputData. I tried using curPortBench.product value as sortBy and it still doesn't work, but it works as value (see code snippet below): <rich:dataTable value="#{piQueryToolOutputBeanPR.statOutData.statVals}" rowKeyVar="rKV" var="curPortBench" rendered="#{not empty piQueryToolOutputBeanPR.statOutData.statistics}"> ... <rich:column id="portBenchName" sortBy="#{curPortBench.product}"> <f:facet name="header"> </f:facet> <!-- h:outputText value="#{piQueryToolOutputBeanPR.statOutData.prodBenchNames[rKV]}"/--> <h:outputText value="#{curPortBench.product}"/> </rich:column> It throws the same exception (FOREACH_BAD_ITEMS). I am not sure why it happens though, because code seems to be similar to the example you provide at http://docs.jboss.org/richfaces/3.3.2.GA/en/devguide/html/rich_column.htm... Could you explain? BTW, is sorting supposed to work only in 3.3.2.CR1 or in 3.3.1.GA as well? " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Leonid Sokolin commented on RF-8469: ------------------------------------ We want to use vector here, because the output should come out in the same order as specified by users in the input request. I don't think, it is worthwhile to make changes in application logic to accommodate the problem with sorting. As for request scope, I suspected that it might be the case as well, but not sure then why export to Excel and PDF functions in the same page work fine. They also rely on the availability of the same data: <a4j:commandLink id="expExcel" action="#{piQueryToolOutputBeanPR.statOutData.genWorkBook}" immediate="false" oncomplete="doDownload('file/abcd?filename=PerformanceReturns_' + #{piQueryToolOutputBeanPR.statOutData.randNum} + '.xls')"> <h:graphicImage value="images/Excel-16.gif" style="border:0"/> </a4j:commandLink> Are you saying that while bean data maybe available, page data no longer is, if the scope is "request only"? This is unfortunate. BTW, I was trying to imitate the logic you provide in the demo example, but it has no mentioning of request scope limitation. <rich:column sortBy="#{cap.state}"> <f:facet name="header"> <h:outputText value="State Name"/> </f:facet> <h:outputText value="#{cap.state}"/> </rich:column> Do you think it is a fundamental problem that couldn't be addressed? In this case, we definitely couldn't use table sorting after this page has been generated. Still, please let me know after the fix is applied to 3.3.2.SR1 and I will try to test it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Leonid Sokolin updated RF-8469: ------------------------------- Attachment: piQueryToolCommon.xhtml We are using popup window to show the data and index is unique parameter to differentiate between them. See attached file for the actual code example: <script language="JavaScript"> function doPopup(beanName, index) { if ( -1 != index ) { popup = window.open("#{popupPage}.faces?beanName=" + beanName + "&amp;index=" + index, "#{popupPage}" + index); popup.focus(); } } </script> ... <managed-property> <property-name>outputIndex</property-name> <value>#{param.index}</value> </managed-property> Could you advise how the value of this parameter should be initialized, so that it is available on subsequent requests such as sorting? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Nick Belaevski resolved RF-8469. -------------------------------- Resolution: Won't Fix After discussion, we decided not to fix "rowKeyVar" limitation; so there's nothing to fix in this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-8469?page=com.atlassian.jira.plugin... ] Nick Belaevski commented on RF-8469: ------------------------------------ Right -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira