On 12/12/12 3:49 AM, Mark Thomas wrote:
> On 12/12/2012 00:33, Danny Coward wrote:
>
> <snip/>
>
>> This is what the API would look like in this (final?) package structure:-
>>
>> javax.websocket.server.*
>> - DefaultServerEndpointConfiguration
>> - ServerEndpointConfiguration
>> - ServerContainer
>> - WebSocketEndpoint
>> - WebSocketPathParam
>>
>> javax.websocket.*
>> -<everything else>
>>
>> Let me know if anyone sees any issues with this arrangement.
> One very minor nit is that it creates a circular dependency between the
> two packages. It could be broken by having separate ContainerProviders
> for client and server. I'm on the fence as to whether this is worth doing.
Well perhaps it wasn't clear, but I don't think we need the
ContainerProvider.getServerContainer() any more. For server side
applications the deployment is handled by scanning/ApplicationConfig. So
the bootstrap is only needed for the client container, so no dependency
from the javax.websocket.* package on the javax.websocket.server.* package
- Danny
>
> Mark
>
--
<http://www.oracle.com> *Danny Coward *
Java EE
Oracle Corporation