websocket-spec
  1. websocket-spec
  2. WEBSOCKET_SPEC-83

Define the portability semantics of ContainerProvider

    Details

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

      Description

      Spec needs to define the portability semantics of ContainerProvider API. At present, it is using a private and undocumented system property to load a provider in the RI's API. If this is the way a provider needs to be located (instead of much preferred ServiceLoader mechanism), this needs to be documented. Note that using a system property doesn't work for a web application that wants use a custom provider(by bundling the provider in a war file).

      Also, API's system property "websocket.clientcontainer.classname" is arbitrary. Usually, it is the class name in many other API, i.e "javax.websocket.ContainerProvider" in this case. WebSocketContainer class name for client container is also misleading.

        Activity

          People

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

            Dates

            • Due:
              Created:
              Updated:
              Resolved: