[WEBSOCKET_SPEC-64] Calirify application deployment semantics Created: 30/Nov/12  Updated: 14/Dec/12  Due: 14/Dec/12  Resolved: 14/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

Issue Links:
Dependency
blocks WEBSOCKET_SPEC-17 Blocking or Asynchronous: Configurati... Resolved
Tags: v010

 Description   

Current scheme is a mix of scanning and programmatic deployment

We are exploring a more webcontainer friendly and efficient manner, using an application config class in the expert group.



 Comments   
Comment by dannycoward [ 14/Dec/12 ]

This has been clarified in the spec.

On the server we use a JAX-RS like scheme: a mix of web container scanning of the WAR files to find endpoints, together with a definition of an ApplicationConfig class that developers can implement if they want finer grained control.

Generated at Sun Apr 26 08:31:36 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.