On Wed, Apr 24, 2019 at 7:03 AM Christopher Dodunski < chrisfromtapes...@christopher.net.nz> wrote:
> From the Java WebSockets specification: > > 4.1 > @ServerEndpoint > "This class level annotation signifies that the Java class it decorates > must be deployed by the implementation as a websocket server endpoint and > made available in the URI-space of the websocket implementation. The class > must be public, CONCRETE, and have a public no-args constructor." :( > Good catch! > Option #2 - opting for concrete service class alone - would mean losing > the ability to set a scope of 'per thread', yes? > I don't think so, but I'm not sure it would work for a server endpoint, as the endpoint instance is probably only requested to the configurator once. I may have to discard the WebSocket annotations and create the server > endpoint programmatically in that case. > Indeed. I'd create an endpoint class which does nothing but delegate method calls to injected service(s). > > Regards, > > Chris. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
