Hi James and thanks for your answer! | Well, an ASO is a "state object" and a service is just that, a service.
What makes a service "just" service is the thing I'm interested in ;) | So, what I do in your situation is have my SecurityContext | service (threaded lifecycle) lookup an ASO (from the | ApplicationStateManager) which holds my current user id (after logging in | I set this). Then, my pages ask the SecurityContext what the current user | is allowed to do. I do have to lookup the user each time a request comes | in, but I've told Hibernate to cache those things in the second-level | cache. Someone asked me to share my code for this before. I don't knkow | if I ever made an example publically available though. Maybe I can put | something like this in my "tapernate-example." I'm trying to beef it up a | bit anyway to show more use cases. Well, that was me I think *g It would be great if you shared your code for this as you haven't done so far. ;) If you don't have the time at the moment you can also just send it to me by mail and I will look through it by myself, no problem! Your solution seems to be exactly what I need/want as I also have an ASO holding the current user (with id) and the SecurityContext sounds like the security object I was thinking about. Sincerly, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
