Endpoint class qualifiers for @WebSocketEndpoint

[glassfishrobot]

Define whether the endpoint class needs to be public, or final ? Can it be abstract etc ? Also make sure it is conformant with other EE specs.

[glassfishrobot]

@glassfishrobot Commented
Reported by jitu

[glassfishrobot]

@glassfishrobot Commented
Was assigned to dannycoward

[glassfishrobot]

@glassfishrobot Commented
dannycoward said:
See section 4.1 of the spec which refers additionally to 7.3.1.

Jitu: Let me know if you think anything is missing, I'm following standard practice with, for example, JAX-RS.

[glassfishrobot]

@glassfishrobot Commented
jitu said:
JAX-RS resources need not have zero-org constructors. See chapter 3.1.2. But it is odd that it doesn't specify any other requirements.

From the definition, the following is allowed (but it cannot be instantiated)

@WebSocketEndpoint
abstract class A {
public A() {
}
}

[glassfishrobot]

@glassfishrobot Commented
dannycoward said:
OK. We certainly can't have non-public abstract classes.

"The class must be public, concrete, and have a public no-args constructor. The class may or may not be final, and may or may not have final methods."

Let me know if there are other types you think we have to allow for v 1.0 as a priority.

[glassfishrobot]

@glassfishrobot Commented
Marked as fixed on Monday, February 4th 2013, 4:56:12 pm

[glassfishrobot]

@glassfishrobot Commented
dannycoward said:
What I proposed has been out to the expert group with no comment, so I am closing this out.

We might look at expanding the possibilities in the next version, but I think this is clear and simple for this version.

[glassfishrobot]

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

[glassfishrobot]

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