[
https://issues.apache.org/jira/browse/MYFACES-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944471#comment-16944471
]
Thomas Andraschko commented on MYFACES-4303:
--------------------------------------------
Can you provide me a simple xhtml + bean for testing purpose?
> f:websocket does not call p:ajax listeners
> -------------------------------------------
>
> Key: MYFACES-4303
> URL: https://issues.apache.org/jira/browse/MYFACES-4303
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Environment: myfaces2.3.4, tomcat 9.0.16
> Reporter: Vladimir.dvorak
> Priority: Major
>
> We have following websocket definition:
>
> {{ <f:websocket channel="dispatcherChannel" user="#\{userBean.getUserId()}"
> scope="application" >}}
> {{ <p:ajax event="broadcastMsgPushOpenEvent"}}
> {{ listener="#\{broadcastMessageBean.onNewBroadcastMsg()}"}}
> {{ update="pnlBroadcastMsg"}}
> {{ ignoreAutoUpdate="true"}}
> {{ global="false"/>}}
> {{ <p:ajax event="broadcastMsgPushCloseEvent"}}
> {{ listener="#\{broadcastMessageBean.onCloseDialogFromPush()}"}}
> {{ update="pnlBroadcastMsg"}}
> {{ ignoreAutoUpdate="true"}}
> {{ global="false"/>}}
> {{ </f:websocket>}}{{}}
>
> {{client browser receives websocket pushes, but does not execute listener's
> actions on server side, otherwise update is executed. We are using forwarding
> from ajax's onstart=".." to <p:remoteCommand> as a workaround now. In the
> past we had been using o:socket with p:ajax without problems.}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
