Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On 16/09/2013 17:37, Nick Williams wrote: > On Sep 16, 2013, at 11:21 AM, Mark Thomas wrote: >> It certainly looks at this point as if the order is "anything you like". >> Personally, I'd prefer something rather more deterministic. > > Agreed. That's why I filed [1]. I've added a comment on some

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On Mon, Sep 16, 2013 at 6:57 PM, Mark Thomas wrote: > On 16/09/2013 15:21, Christopher Schultz wrote: > > Mark, > > > > On 9/16/13 5:09 AM, Mark Thomas wrote: > >> The only requirement on ordering is at the end of section 8.2 > >> which requires that application SCIs are discovered before > >> co

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On Sep 16, 2013, at 11:21 AM, Mark Thomas wrote: > On 16/09/2013 16:57, Mark Thomas wrote: >> The issue is with the lack of clarity from the EG with respect to >> ordering. I read section 8.2 one way but it is open to interpretation. > > I've dug back through the Servlet 3.0 mailing list. > > T

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 9/16/13 11:57 AM, Mark Thomas wrote: > On 16/09/2013 15:21, Christopher Schultz wrote: >> Mark, >> >> On 9/16/13 5:09 AM, Mark Thomas wrote: >>> The only requirement on ordering is at the end of section 8.2 >>> which requires that applica

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On 16/09/2013 16:57, Mark Thomas wrote: > The issue is with the lack of clarity from the EG with respect to > ordering. I read section 8.2 one way but it is open to interpretation. I've dug back through the Servlet 3.0 mailing list. The text at the end of section 8.2 is aimed at the case where th

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On Monday, September 16, 2013, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Mark, > > On 9/16/13 5:09 AM, Mark Thomas wrote: > > The only requirement on ordering is at the end of section 8.2 > > which requires that application SCIs are discovered before > > co

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On 16/09/2013 15:21, Christopher Schultz wrote: > Mark, > > On 9/16/13 5:09 AM, Mark Thomas wrote: >> The only requirement on ordering is at the end of section 8.2 >> which requires that application SCIs are discovered before >> container SCIs. That is the opposite to what is being requested >>

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 9/16/13 5:09 AM, Mark Thomas wrote: > The only requirement on ordering is at the end of section 8.2 > which requires that application SCIs are discovered before > container SCIs. That is the opposite to what is being requested > here. > >

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On Sep 16, 2013, at 4:09 AM, Mark Thomas wrote: > On 16/09/2013 10:00, Niki Dokovski wrote: >> On Fri, Sep 13, 2013 at 9:27 PM, Niki Dokovski wrote: >> >>> >>> >>> >>> On Fri, Sep 13, 2013 at 8:55 PM, Nick Williams < >>> nicho...@nicholaswilliams.net> wrote: >>> On Sep 13, 2013,

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On Mon, Sep 16, 2013 at 12:09 PM, Mark Thomas wrote: > On 16/09/2013 10:00, Niki Dokovski wrote: > > On Fri, Sep 13, 2013 at 9:27 PM, Niki Dokovski > wrote: > > > >> > >> > >> > >> On Fri, Sep 13, 2013 at 8:55 PM, Nick Williams < > >> nicho...@nicholaswilliams.net> wrote: > >> > >>> > >>> On Sep

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On 16/09/2013 10:00, Niki Dokovski wrote: > On Fri, Sep 13, 2013 at 9:27 PM, Niki Dokovski wrote: > >> >> >> >> On Fri, Sep 13, 2013 at 8:55 PM, Nick Williams < >> nicho...@nicholaswilliams.net> wrote: >> >>> >>> On Sep 13, 2013, at 12:42 PM, Igor Urisman wrote: >>> I couldn't agree more. W

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On Fri, Sep 13, 2013 at 9:27 PM, Niki Dokovski wrote: > > > > On Fri, Sep 13, 2013 at 8:55 PM, Nick Williams < > nicho...@nicholaswilliams.net> wrote: > >> >> On Sep 13, 2013, at 12:42 PM, Igor Urisman wrote: >> >> > I couldn't agree more. WebSocket is provided by the container. But the >> > ti

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On Fri, Sep 13, 2013 at 8:55 PM, Nick Williams < nicho...@nicholaswilliams.net> wrote: > > On Sep 13, 2013, at 12:42 PM, Igor Urisman wrote: > > > I couldn't agree more. WebSocket is provided by the container. But the > > time any app code gets to run, Spring of Fall, container ought to be > don

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On Sep 13, 2013, at 12:42 PM, Igor Urisman wrote: > I couldn't agree more. WebSocket is provided by the container. But the > time any app code gets to run, Spring of Fall, container ought to be done. > -Igor. > > > On Fri, Sep 13, 2013 at 10:38 AM, Christopher Schultz < > ch...@christophersch

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

I couldn't agree more. WebSocket is provided by the container. But the time any app code gets to run, Spring of Fall, container ought to be done. -Igor. On Fri, Sep 13, 2013 at 10:38 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Konstantin, On 9/13/13 7:50 AM, Konstantin Kolinko wrote: > I see no issue here, as both WebSocket implementation and Spring's > WebApplicationInitializer rely on use of > "javax.servlet.ServletContainerInitializer" to initialize > themselves. >

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

On Fri, Sep 13, 2013 at 7:56 AM, Igor Urisman wrote: > Dear all, > > It appears that if I obtain the ServletContext object via Spring's > WebApplicationInitializer > mechanism< > http://static.springsource.org/spring/docs/3.1.x/javadoc-api/org/springframework/web/WebApplicationInitializer.html > >

Re: 8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

2013/9/13 Igor Urisman : > Dear all, > > It appears that if I obtain the ServletContext object via Spring's > WebApplicationInitializer > mechanism, > it is not yet seeded with the W

8.0.0 RC1: WebSocket ServerContainer servlet context attribute gets set too late.

Dear all, It appears that if I obtain the ServletContext object via Spring's WebApplicationInitializer mechanism, it is not yet seeded with the WebSocket ServerContainer object. Alt