users@websocket-spec.java.net

[jsr356-users] [jsr356-experts] Re: More more programmatic deployment

From: Danny Coward <danny.coward_at_oracle.com>
Date: Wed, 27 Feb 2013 16:13:17 -0800

OK given the very late stage we are in with v 1.0 of the spec, we are
prototyping this solution to conclude the 'programmatic deployment'
issue. Should have news tomorrow.

Cheers,

- Danny

On 2/27/13 10:03 AM, Mark Thomas wrote:
> On 27/02/2013 09:17, Danny Coward wrote:
>> OK thanks Mark and Rossen. Jitu on our team has suggested instead of:-
>>
>> ServerContainer* extends WebSocketContainer {
>> public void deploy(Class<?> pojo) throws DeploymentException;
>> public void deploy(ServerEndpointConfiguration sec) throws
>> DeploymentException;
>> }
>>
>> we go the whole hog and do:-
>>
>> ServerContainer* extends WebSocketContainer {
>> public void deploy(Set<Class<?>> pojos) throws DeploymentException;
>> public void deploy(Set<ServerEndpointConfiguration> configs) throws
>> DeploymentException;
>> }
>>
>> Its basically the API call the containers have to have to support
>> ServerApplicationConfiguration in any case.
>>
>> Let me know if you have a string preference for either.
>
> No strong preference - happy with either.
>
> Mark
>


-- 
<http://www.oracle.com> 	*Danny Coward *
Java EE
Oracle Corporation