On Friday, May 27, 2011, Miguel wrote: > Following my previous email and agreeing with you on this, I might, of > course, get off the request hook by changing the request injection with > injecting, for example, those two properties (username and ipaddress) to > this class, but the underlying problem is the same: I'm not seeing how I > can inject that requests' username and IP address to that class...
I'd probably keep a session-scoped bean containing the desired properties and inject that into the Hibernate interceptor. Spring understands session-scoped beans; fill the bean on login, etc. I guess I thought that Hibernate interceptors were normally singletons, but maybe not. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org