[ https://issues.apache.org/jira/browse/MYFACES-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631069#comment-17631069 ]
Werner Punz commented on MYFACES-4496: -------------------------------------- Apparently the entire push api now gets a refactoring: [https://github.com/apache/myfaces/pull/327] I will retest the issue once the pull request is merged. > Server side Websocket/Push Implementation not working > ------------------------------------------------------ > > Key: MYFACES-4496 > URL: https://issues.apache.org/jira/browse/MYFACES-4496 > Project: MyFaces Core > Issue Type: Bug > Affects Versions: 4.0.0-RC2 > Reporter: Werner Punz > Priority: Blocker > > While fixing several reported bugs in the new faces.js code I ran against a > non working push implementation on the 4.0.0-RC2 codebase. > Problem was a simple new WebSocket(<provided url by f:websockt>) could not > establish a working connection. > The problem is definitely somewhere in the server, either not registering the > Websocket endpoint or delivering the wrong connection token. > A example implemented via the Websocket servlet api and plain html works in > the same configuration, se we can rule out the server environment (Embedded > Tomcat 10). You can use straight the code from master to replicate this > problem (I have decorated the faces.js api accordingly just to try a > connection on the jsf side instead of going into the code) > > An example can be found at: [https://github.com/werpu/websocketproblem] > Run instructions are included in the integrated readme, it uses an embedded > tomcat/openwebbeans/myfaces 4.0.0 stack so a simple > mvn clean clean install -DskipTests exec:java -Pstandalone -f pom.xml starts > the server and installs all libraries, the rest is documented in the github > repo readme. > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)