WebSocketContainer.connectToServer ease of use / API change

[glassfishrobot]

(from Scott)

The new connectToServer is difficult to use.

Instead of a Class parameter, it should be an object. The container shouldn't need to instantiate the object, and the Class model makes it difficult to connect between the client application and the client endpoint. (Because any shared state/object needs to be passed through a custom ClientEndpointConfiguration.)

The API should be simplified to:

WebSocketContainer {
Session connectToServer(Object endpoint, URI path);

Session connectToServer(Object endpoint, URI path, ClientEndpointConfiguration cec);
}

If the "endpoint" object is already of type Endpoint, it's used directly. Otherwise, a skeleton/proxy is created, i.e. annotation stuff.

There's no need for separate methods for Endpoint vs annotation.

[glassfishrobot]

@glassfishrobot Commented
Reported by dannycoward

[glassfishrobot]

@glassfishrobot Commented
Issue-Links:
is related to
WEBSOCKET_SPEC-69

[glassfishrobot]

@glassfishrobot Commented
Was assigned to dannycoward

[glassfishrobot]

@glassfishrobot Commented
dannycoward said:
awaiting last feedback on whether to add these methods

[glassfishrobot]

@glassfishrobot Commented
dannycoward said:
This has been added in v014, with the disclaimers that dependency injection may not work.

[glassfishrobot]

@glassfishrobot Commented
Marked as fixed on Friday, March 1st 2013, 2:20:16 pm

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA WEBSOCKET_SPEC-116

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/websocket-spec/issues/116
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @pavelbucek
• Original Issue Closed By:@glassfishrobot