[WEBSOCKET_SPEC-27] Clean up specifiction of allowable parameters on @WebSocketMessage methods Created: 12/Oct/12  Updated: 04/Dec/12  Resolved: 04/Dec/12

Status: Resolved
Project: websocket-spec
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: dannycoward Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: v009

 Description   

Section 4.3.3

  • Why does the entity have to come in the first parameter? Can't we just say the first (and only) parameter that is not of type Session and isn't annotated with @WebSocketPathParam annotation?
  • Why can't the entity param be of any type? Otherwise decoders are never utilized.

Also, @WebSocketMessage javadoc.



 Comments   
Comment by dannycoward [ 25/Oct/12 ]

Specifically: allow all types for which there are decoders to be allowed here, and also the async callbacks.

Comment by dannycoward [ 04/Dec/12 ]

fixed per comment in upcoming v009

Generated at Tue Feb 09 09:02:46 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.