From: Bill B. <bb...@re...> - 2011-02-21 22:24:07
|
Why not have the user login via normal servlet mechanisms and set up a session. Inject the HttpServletRequest into your Resteasy objects. Grab information in and out of the request object. No sense in you reinventing a servlet container. On 2/21/11 12:24 PM, Neil Chaudhuri wrote: > It looks like I will need to set a cookie to maintain state on the client, and I am considering doing so by using a PostProcessInterceptor. However, it isn't obvious to me how to do this though with a ServerResponse object. I would imagine it might take a call to setMetadata, but how does that class distinguish cookies from other metadata like headers? > > Any insight in how cookies are set is appreciated. > > Thanks. > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Resteasy-developers mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-developers -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |