[richfaces-issues] [JBoss JIRA] (RF-13787) Push with EAP 6.3 not using WebSockets

[Matej Novotny (JIRA)]

     [ https://issues.jboss.org/browse/RF-13787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny updated RF-13787:
-------------------------------

    Summary: Push with EAP 6.3 not using WebSockets  (was: Push not using WebSockets)


> Push with EAP 6.3 not using WebSockets
> --------------------------------------
>
>                 Key: RF-13787
>                 URL: https://issues.jboss.org/browse/RF-13787
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 4.5.0.Alpha3
>         Environment: RichFaces 4.5.0-SNAPSHOT
> Metamer 4.5.0-SNAPSHOT
> Mojarra 2.1.28-jbossorg-2
> JBoss AS 7.4.0.Final-redhat-12 (EAP 6.3)
> Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux
> Chrome 36.0.1985.143 @ Linux x86_64
> _____
> Same with latest FF, but Chrome has better verification tools in this case.
>            Reporter: Matej Novotny
>             Fix For: 4.5.0.Beta1
>
>
> When using push, connection should be established via WebSockets.
> This does not happen and the old method is used. I also tried a workaround which was needed in earlier versions of EAP - [manually enabling websockets|http://blog.arungupta.me/2014/05/websocket-jboss-eap-6-3/].
> I used EAP 6.3 and Metamer/Showcase. Please see steps to reproduce.
> As for verification of WebSockets usage, Chrome dev tools can detect connection establishment as described [here|http://blog.kaazing.com/2012/05/09/inspecting-websocket-traffic-with-chrome-developer-tools/].



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)