websocket-spec
  1. websocket-spec
  2. WEBSOCKET_SPEC-7

Boostrapping websocket containers in web container and standalone

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      For now the API has a ContainerProvider class that can use the service loader mechanism to load
      different implementations of the Client and Server containers. This will be ok for the Java SE client
      API, but probably not for Java EE.

      We will explore other mechanisms in the Java EE case. Perhaps making the ServerContainer a CDI managed bean that can
      be injected into developer code, perhaps into a ServletContext initializer, for example. Or an annotation that the web
      container must scan for that indicates that a given class implementing one of the Container interfaces must be loaded at
      startup.

        Activity

        dannycoward created issue -
        dannycoward made changes -
        Field Original Value New Value
        Due Date 2012-11-09 00:00:00.0
        dannycoward made changes -
        Assignee dannycoward [ dannycoward ]
        Hide
        dannycoward added a comment -

        Some notes on client-side and server-side deplotment

        Server Side
        automatic POJO scanning
        No scan for Endpointsubclass, programmtically deploy
        deploy method should work for POJO

        Client Side
        no scan, programmtic deployment (client needs to control when to connect)
        programmtic POJO deployment.

        Show
        dannycoward added a comment - Some notes on client-side and server-side deplotment Server Side automatic POJO scanning No scan for Endpointsubclass, programmtically deploy deploy method should work for POJO Client Side no scan, programmtic deployment (client needs to control when to connect) programmtic POJO deployment.
        Hide
        dannycoward added a comment -

        We have added the appropriate client deployment API for POJOs and Endpoints and adjusted the server API for deployment. The spec document has been updated for the WAR scanning for POJOs.

        Show
        dannycoward added a comment - We have added the appropriate client deployment API for POJOs and Endpoints and adjusted the server API for deployment. The spec document has been updated for the WAR scanning for POJOs.
        dannycoward made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Tags v008
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            dannycoward
            Reporter:
            dannycoward
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved: