[ https://jira.jboss.org/jira/browse/RF-7240?page=com.atlassian.jira.plugin... ] Nick Belaevski updated RF-7240: ------------------------------- Issue Type: Feature Request (was: Bug) -- 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-7240?page=com.atlassian.jira.plugin... ] Nick Belaevski resolved RF-7240. -------------------------------- Resolution: Won't Fix Assignee: Alexander Dubovsky -- 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-7240?page=com.atlassian.jira.plugin... ] Dave Chen commented on RF-7240: ------------------------------- In our application, for instance, an entity is created using a command link (which is dynamically generated). After the entity is created during Invoke Application phase, the command link is removed because it is not applicable any more. ------------------------------------- | Form data to create entity | ------------------------------------- command1, command2, the command links are rendered using <t:dataList> <t:dataList value="#{bean.commandList}" var="command"> <a4j:commandLink value="#{command.name} action="#{command.exec}" reRender="#{command.reRender}" /> </t:dataList> Similarly, in case of pagination, the command list will change when users navigate into the different page. First, previous, next, last In the first page, the "First" is a label. On the 2nd page, the "First" is a command link, etc. We raised this issue because a list of commands are dynamically created on context in our application. For a static jsf page, there will no such issue. The list of commands are changed after taking action in the Invoke App phase. So during the render phase, a4j gets the wrong value for reRender attribute. Trinidad does not have this issue for PPR. There are some issues in our application because of the way A4J behaves. It would be very helpful if this feature can be added, or some workaround can be provided. -- 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-7240?page=com.atlassian.jira.plugin... ] Dave Chen reopened RF-7240: --------------------------- see previous comment. Our application can not work with a4j because of 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-7240?page=com.atlassian.jira.plugin... ] Nick Belaevski resolved RF-7240. -------------------------------- Resolution: Rejected Rejected for the same reason as before. You can use EL-expression: reRender="#{bean.idsList}" or use AjaxContext API to define components to re-render -- 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