Issue Details (XML | Word | Printable)

Key: WEBSOCKET_SPEC-42
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: dannycoward
Reporter: dannycoward
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
websocket-spec

@WebSocketPathParameter clarifications

Created: 17/Oct/12 07:39 PM   Updated: 08/Dec/12 12:04 AM  Due: 16/Nov/12   Resolved: 08/Dec/12 12:04 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags: v009
Participants: dannycoward


 Description  « Hide
  • 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.


No work has yet been logged on this issue.