The attached patch provides a way to do push events outside of wicket.

      Current native websocket support only allows pushing wicket components to browser as a response to ajax or websocket message. With this feature it is possible to push external event for processing in wicket context so that wicket code can normally update components, which are then pushed over websocket connection to the browser.

      The new api in WebSocketPushBroadcaster can be used in two ways:
      a) push to specific websocket connection
      b) broadcast push to all websockets connected to specific Page

      When either is invoked:
      1) a new wicket context is created
      2) a new wicket event with a IWebSocketPushMessage is broadcast to relevant components
      3) the components are added to the event
      4) the modified components are pushed to browser over websocket connection

        Issue Links


          Andreas Kuhtz made changes -
          Link This issue relates to WICKET-4924 [ WICKET-4924 ]
          Martin Grigorov made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Fix Version/s 6.4.0 [ 12323450 ]
          Resolution Fixed [ 1 ]
          Martin Grigorov made changes -
          Remote Link This issue links to "Mail discussion (Web Link)" [ 11402 ]
          Mikko Tiihonen made changes -
          Field Original Value New Value
          Attachment WICKET-4832-websocket-broadcast.patch [ 12550334 ]
          Mikko Tiihonen created issue -


            • Assignee:
              Martin Grigorov
              Mikko Tiihonen
            • Votes:
              0 Vote for this issue
              3 Start watching this issue


              • Created: