Open speedfl opened 2 years ago
/cc @manovotn, @mkouba
Is there a workaround for this ?
did anyone get it? @speedfl @mkouba
Hm, the specification does not seem to define the lifecycle of the ServerEndpointConfig.Configurator
provided by the user so :shrug:. I mean Quarkus can try to lookup the bean first but we should be careful here...
Is there a workaround for this ?
You can lookup the beans using the CDI.current().select(SomeBean.class).get()
or Arc.container().instance(SomeBean.class).get()
directly in the AuthConfigurator
. However, keep in mind that the SomeBean
could be identified as an unused bean and removed. You might need to mark the bean as unremovable.
Description
Hello Quarkus team
It could be nice to add javax.websocket.server.ServerEndpointConfig.Configurator in CDI context so we can apply custom logic inside for authentication for example.
Implementation ideas
No response