[Bug 65262] Enable websocket endpoints to be IoC friendly (javaee integration at least)

2021-05-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65262 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 65262] Enable websocket endpoints to be IoC friendly (javaee integration at least)

2021-05-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65262 --- Comment #8 from Mark Thomas --- I've applied a fix for Endpoints to 10.0.x, 9.0.x and 8.5.x. I'll look at Encoders and Decoders next so if there are any issues with the current approach do let me know. -- You are receiving this mail

[Bug 65262] Enable websocket endpoints to be IoC friendly (javaee integration at least)

2021-04-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65262 --- Comment #7 from romain.manni-bucau --- @Mark functionally I can leave with current validation but theorically the validation is only known of the IoC but it is not super aligned on the spec. To illustrate it take a CDI or Spring encoder,

[Bug 65262] Enable websocket endpoints to be IoC friendly (javaee integration at least)

2021-04-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65262 --- Comment #6 from Mark Thomas --- @Rémy I think I can see a way to do that. We'll need to check which Configurator was used in the WsSession constructor to make sure we don't call the InstanceManager twice. It does mean that the timing of

[Bug 65262] Enable websocket endpoints to be IoC friendly (javaee integration at least)

2021-04-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65262 --- Comment #5 from Remy Maucherat --- (In reply to romain.manni-bucau from comment #4) > @Mark: this issue is about the default configurator, fully agree when a > custom configurator is used tomcat will not care. I agree if using the default

[Bug 65262] Enable websocket endpoints to be IoC friendly (javaee integration at least)

2021-04-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65262 --- Comment #4 from romain.manni-bucau --- @Mark: this issue is about the default configurator, fully agree when a custom configurator is used tomcat will not care. I also agree encoders/decoders IoC support is not in the specification but not

[Bug 65262] Enable websocket endpoints to be IoC friendly (javaee integration at least)

2021-04-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65262 --- Comment #3 from Mark Thomas --- Section 3.1.7 of the WebSocket specification requires endpoint instances are created via ServerEndpointConfig.Configurator.getEndpointInstance(). Users are free to supply their own Configurator

[Bug 65262] Enable websocket endpoints to be IoC friendly (javaee integration at least)

2021-04-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65262 --- Comment #2 from romain.manni-bucau --- Hmm, endpoint api starts from a class on server side so should use the related instance manager instantiator and not only the injection "newInstance" probably. For an annotated endpoint you likely

[Bug 65262] Enable websocket endpoints to be IoC friendly (javaee integration at least)

2021-04-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65262 --- Comment #1 from Mark Thomas --- WebSocket endpoints already use the InstanceManager. https://github.com/apache/tomcat/blob/master/java/org/apache/tomcat/websocket/WsSession.java#L180