2008/1/31, Scott Battaglia <[EMAIL PROTECTED]>: > > <snip /> > > True, it will hold on to it. Its designed for the "in-memory" case. If > we don't store the reference in memory then I don't know how to gain a > reference to that session. I don't think the Servlet API exposes a method, > does it? I'd prefer not to use container specific versions if possible > (because I'm assuming individual containers have a method of retrieving a > session based on id). >
I suggest using simple hashmap-based implementation but providing extension point to allow customizations. Servlet API doesn't have means of accessing session, however application developers will at least have possibility to write container-specific management. <snip /> > > I resolved your JIRA issue about the "totally broken" part :-). It should > actually now work in Spring. I added some test cases and a simple Spring > configuration example. If we don't resolve the above Session stuff soon > I'll cut an RC3 so other people can try out the fix for the Spring stuff > (though you can also check it out from Subversion) > Great! Except for mentioned bug cas-client-3.1-rc2 perfectly works for us. Signing in, proxy stuff and single sign out. The only thing we didn't try is AuthenticationFilter because we use Acegi Security integration. P.S. CAS rocks ;)
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
