[WEBSOCKET_SPEC-42] @WebSocketPathParameter clarifications Created: 17/Oct/12  Updated: 08/Dec/12  Due: 16/Nov/12  Resolved: 08/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: dannycoward
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: v009

  • Does the order of @WebSocketPathParam in the method matters ? Can it be the last one, first one, in the middle ?
  • Same section, what is the usecase for parameter injection in lifecycle methods ? Those are implicitly called by the container anyway and never explicitly invoked as part of a URI.
  • When @WebSocketPathParam is used, we should also define integration with Bean Validation. This will allow to define constraints on the bean when data conversion needs to happen.

Comment by dannycoward [ 08/Dec/12 ]

We may consider bean validation for the next version - the other issues are now resolved.

Generated at Thu Jan 19 07:57:41 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.