[ https://issues.jboss.org/browse/RF-13482?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13482 at 1/21/14 12:59 AM: ----------------------------------------------------------- EAP 6.1.1 debugging: I have found that the popup is not rendered because the commandLink is not executed. During debugging we have revealed that doDecode method of the commandLinked's renderer is not executed. It is caused by a fact that when the component should be executed during APPLY_REQUEST_VALUES phase, the tree is traversed by EPVC and it uses JSF's native traversal mechanism to visit all components that are in EPVCI's {{executedIds}} collection (which is {{["j_idt330"]}}). But the debugging revealed that where the component {{"j_idt330"}} should be, the same component lies but with different ID ({{"j_idt666"}}). Which is somehow related to partial state saving (I would actually try to this on MyFaces). Initially I have though that it is caused by UIOutputPanelWorkaround component that wraps the commandLink, but that's not the case (when disabled it didn't help). What helped to overcome this issue is turning {{javax.faces.PARTIAL_STATE_SAVING=false}}. This can be used as workaround. However the root cause is not known yet and as [~michpetrov] pointed out, turning partial state saving off causes drag-n-drop to stop to work. was (Author: lfryc): I have found that the popup is not rendered because the commandLink is not executed. During debugging we have revealed that doDecode method of the commandLinked's renderer is not executed. It is caused by a fact that when the component should be executed during APPLY_REQUEST_VALUES phase, the tree is traversed by EPVC and it uses JSF's native traversal mechanism to visit all components that are in EPVCI's {{executedIds}} collection (which is {{["j_idt330"]}}). But the debugging revealed that where the component {{"j_idt330"}} should be, the same component lies but with different ID ({{"j_idt666"}}). Which is somehow related to partial state saving (I would actually try to this on MyFaces). Initially I have though that it is caused by UIOutputPanelWorkaround component that wraps the commandLink, but that's not the case (when disabled it didn't help). What helped to overcome this issue is turning {{javax.faces.PARTIAL_STATE_SAVING=false}}. This can be used as workaround. However the root cause is not known yet and as [~michpetrov] pointed out, turning partial state saving off causes drag-n-drop to stop to work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira