[ 
https://issues.apache.org/jira/browse/MYFACES-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251759#comment-15251759
 ] 

Thomas Herzog commented on MYFACES-4043:
----------------------------------------

Thanks for the response.
I will report this issue to primefaces.


> PostAddToViewEvent in RENDER_RESPONSE not fired on postback requests when 
> partial-state-saving is turned off
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-4043
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4043
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.2.9
>         Environment: OS:      Windows 10
> IDE:      Intellij
> Server: Tomcat 8.0.30/Wildfly 10
> JSF-lib: Primefaces 5.3
>            Reporter: Thomas Herzog
>            Assignee: Leonardo Uribe
>
> We use priemfaces growl which is an component where message can be displayed. 
> This component  is marked with the interface AutoUpdatable, which means that 
> these components do not need to be included in response update ids explicitly 
> and can be added to the response automatically. This happens in the class 
> *org.primefaces.event.AutoUpdateComponentListener* where a *SystemEvent* is 
> observed. On postback request the growl will be added to the response update 
> ids if configured to do so.
> The problem is, that this listener is only called ones on initial get request 
> and not on the following postback request if partial-state-saving is turned 
> off. If partial-state-saving is turned on, then the listener gets called on 
> postback request too.
> It seems that the PostAddToViewEvent is not fired on postback request if 
> PartialStateSaving is turned off but will be fired if turned on.
> See the following link for an running example:
> https://github.com/Curecomp/myfaces-issues/tree/master/2.2.9/disabled_psv_post_add_view_event_not_fired



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to