On Tue, Jun 4, 2013 at 12:01 AM, Rossen Stoyanchev < rstoyanc...@gopivotal.com> wrote:
> On Mon, Jun 3, 2013 at 10:27 AM, Niki Dokovski <nick...@gmail.com> wrote: > > > On Mon, Jun 3, 2013 at 3:44 PM, Niki Dokovski <nick...@gmail.com> > wrote:Further > > on, if you choose to use connectToServer call that has the > > ClientEndpointConfig param you are losing the annotation approach as the > > first param of this call has to be an instance of an Endpoint. Hence your > > class can not be just annotated. hmmm Mark where can we bring this > > discussion? > > > This is not very obvious from the API but ClientEndpointConfig (and > ServerEndpointConfig) are not meant to be used with annotated endpoints. In > other words, I think the methods accepting those types are for use with > type-based endpoints (i.e. javax.websocket.Endpoint). So as far as I can > see user properties can be updated before the session starts only for > type-based endpoints. > Exactly, What is the rationale behind this? Still an annotated endpoint can supply javax.websocket.ClientEndpointConfig.Configurator but has no access to the user properties from there. May be the javax.websocket.ClientEndpointConfig.Configurator can be extended to provide access to the map. cheers > > Rossen >
