Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If my ThreadLocal singleton is only going to be alive for the life of the request anyhow, then why not just use a request attribute? Is this just an easy way to get at a context in a single thread without having to pass through or get to the request object?
My opinion is, that using a request attribute is more preferable than using a
ThreadLocalvariable.It makes code cleaner and you don’t have to worry about cleaning the
ThreadLocal(as it might be re-used be in context of another request which re-uses the same thread).Though, properly designed and coded local request storage via
ThreadLocalis fine, if usage ofThreadLocalis encapsulated and you don’t simply share an instance between different classes (and it’s life-cycle is properly handled).