Right it is written it needs to use servlet scanning but not the min servlet version (3.0 or 3.1) Le 29 oct. 2013 13:42, "Niki Dokovski" <nick...@gmail.com> a écrit :
> On Tue, Oct 29, 2013 at 1:59 PM, Mark Thomas <ma...@apache.org> wrote: > > > On 29/10/2013 11:46, Niki Dokovski wrote: > > > On Tue, Oct 29, 2013 at 1:40 PM, Mark Thomas <ma...@apache.org> wrote: > > > > > >> On 29/10/2013 11:17, Niki Dokovski wrote: > > >> > > >>> I agree with Mark and looked further in the spec looking for a list > of > > >>> dependent specifications. Actually the only dependency I found is > > >> described > > >>> in 7.1.1 Websocket Endpoints and Dependency Injection and it deals > with > > >> CDI > > >>> and no exact version of the Servlet specification is defined. Perhaps > > >> it's > > >>> no big deal but it's always good to avoid gray areas. Mark did you > > >>> discussed this in EG? What about having this as an improvement for > the > > >> next > > >>> version of the spec? > > >> > > >> Huh? > > >> > > >> The Java WebSocket spec was explicitly designed not to have dependency > > >> on any Servlet specification. There is no requirement for a WebSocket > > >> implementation to be part of a J2EE container. > > >> > > > > > > Java EE 7 Full Profile or Web profile compliant implementations should > > > provide JSR 356 defined container. It is listed at least in Web Profile > > > Specification "WP 2.1 Required Components". Or I'm missing something? > > > > Java EE requires WebSocket. WebSocket does not require Java EE. > > It is perfectly acceptable to develop a stand-alone Java WebSocket > container > > that implements no other J2EE specs. > > > > > WebSocket container can be used in Java SE env only but for a standard JSR > 356 compliance implementation an existing servlet container is needed. > Basically you are correct if you don't refer to JSR 356. But my question > was related to improving the spec, triggered by Romain's question. > > > > > > Mark > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > >
