Paul Furbacher <pfurbache..ac.com> wrote:
> Thanks, but I've read that a few times, but it's the requirement
> to bind to a ThreadLocal that is the area of uncertainty.
It's not really a requirement. You can store/restore your DataContext
however you feel is most appropriate. For web apps, that's generally stored
in either the session (if you can guarantee that all session access is
serialized) or in ThreadLocal otherwise.
> But
> that's small fish compared to the overlooked import of my original
> message, that of implementing a stand-alone configurer for this.
Didn't overlook it. Just don't know enough to comment :)
My own Spring/Cayenne/JSF project retrieves and provides the DataContext
using a JSF PhaseListener rather than dependency-injection/interceptor.
-Mike
This archive was generated by hypermail 2.0.0 : Thu Jun 02 2005 - 17:34:18 EDT