Andreas Schildbach wrote:

Hello everyone,

I was just wondering why my HttpSessionIntegrationFilter does not save my custom user object to the next request...

For my application, I have extended SecureContext to SecureUserContext, adding my domain object for users as a property.

Looking at the source of AbstractIntegrationFilter I unfortunately discovered that it just saves the authentication object, not any custom object(s) attached to it. Why don't you save just the whole SecureContext? Then it would (theoretically) never be needed to create a SecureContext again, and everything contained in it would be saved, too?

I just committed to CVS a significant refactoring of the "well known location" model.

They are aimed at delivering full and automatic support for extensions to the Context (eg as Andreas did so above), greatly simplifying the understanding of ContextHolder <--> HttpSession integration, ensuring the context package can be used standalone (ie without any Acegi Security dependencies), and also avoiding the needless creation of HttpSessions to support things like Basic authentication.

The docs/xdocs/upgrade directory contains full information on changes to support this upgrade, and I've also updated the reference documentation. Those using CVS should have a look in the upgrade docs, as simply deploying the latest JAR built from CVS will not work.

On a related matter, I've updated CVS to reflect our next project release as 0.8.0.

Comments welcome.

Best regards
Ben



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Home: http://acegisecurity.sourceforge.net
Acegisecurity-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer

Reply via email to