The locking issue has been an ongoing discussion for quiet some time. It is a delicate and complex issue, which is not as simple as wrapping getBean() or constructBean() in a lock. Locking your beanFactory creation is a start. Locking your application initialization is a next step, but we do need to implement a better strategy inside constructBean. Believe me, I have lost sleep over this issue. So, ColdSpring engineers, if any of you would like to get together and discuss, please get me or Dave on IM, or we can do a group skype when any of you are available. Chris On Apr 26, 2007, at 5:14 AM, Tom Chiverton wrote:
|
- [coldspring-dev] Object already exists in cache exception Stuart Miller
- [coldspring-dev] Object already exists in cache exce... Russ Johnson
- [coldspring-dev] Object already exists in cache exce... Peter J. Farrell
- [coldspring-dev] Object already exists in cache exce... Russ Johnson
- [coldspring-dev] Object already exists in cache exce... Jon Gunnip
- [coldspring-dev] Object already exists in cache exce... Tom Chiverton
- [coldspring-dev] Object already exists in cache exce... Chris Scott
- [coldspring-dev] Object already exists in cache exce... Tom Chiverton

