[ https://issues.jboss.org/browse/RF-12536?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12536 at 3/6/14 6:22 AM: --------------------------------------------------------- As we are now adding RichFaces specific extensions to any request, the only remaining differences are: * AjaxOutputs (implicitly rendered areas) are not rendered * meta-components can't be addressed I think we could enable this but make it configurable - the switch would be pretty easy: https://github.com/richfaces/richfaces/blob/RF-13505-refactor-epvc-3/fram... However, since the request is not from RichFaces.ajax API, we don't have any clue about activator component. Note that if we override jsf.ajax.request to take over this logic from RichFaces.ajax, there are requests that doesn't have to go through this API - e.g. PrimeFaces use jQuery.ajax. So the logic should probably be - if we don't have any knowledge of activatorComponent (org.richfaces.ajax.component request parameter), we should just skip activator visiting for collecting renderIds/executeIds and use parent implementation. was (Author: lfryc): As we are now adding RichFaces specific extensions to any request, the only remaining differences are: * AjaxOutputs are not rendered * meta-components can't be addressed I think we could enable this but make it configurable - the switch would be pretty easy: https://github.com/richfaces/richfaces/blob/RF-13505-refactor-epvc-3/fram... However, since the request is not from RichFaces.ajax API, we don't have any clue about activator component. Note that if we override jsf.ajax.request to take over this logic from RichFaces.ajax, there are requests that doesn't have to go through this API - e.g. PrimeFaces use jQuery.ajax. So the logic should probably be - if we don't have any knowledge of activatorComponent (org.richfaces.ajax.component request parameter), we should just skip activator visiting for collecting renderIds/executeIds and use parent implementation. -- 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