When we last investigated CDI on JSR356 (javax.websocket) it was undefined. Neither the CDI spec folks on the Weld project, nor the JSR356 spec group had any answers. There are open/unresolved bugs at both specs about it.
I suspect that the undefined nature of the lifecycle of a WebSocket is the root cause of it. The early discussions felt that WebSocket, being born from an HTTP Upgrade should follow the same lifecycle and rules as an HTTP request. But this has proved problematic. Even concepts like HttpSession duration/lifecycle/updates, and Authentication (what to do if auth is revoked during a websocket session) is undefined in JSR356. Joakim Erdfelt / [email protected] On Tue, Nov 10, 2015 at 6:16 AM, Mohan Kumar G <[email protected]> wrote: > Hello, > > Is there a way to have Session scoped object? > > *Service designed :* Jetty (as stand alone) + Websocket + CDI > > *Requirement:* Want to have an object called Storage which should get > create when client establishes websocket connection and destruct when > websocket connection is closed. Essentially websocket session and Storage > object should have one to one mapping. > > Thanks and Regards > Mohan > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
