|
From: <hei...@jb...> - 2006-07-04 07:31:14
|
This does still work on the static ConcurrentHashMap, right? This will probably work for testing, but how do you want to prevent unexpected results in production? Basically everyone can enable/disable caching of XB all the time. Plus there's a synchronization overhead and probably a memory leak when the map grows over time. Why don't we associate ClassInfos with Marshaller/Unmarshaller instances? ThreadLocal would be another option. I think the suggested API works, but I am concerned about unwanted side effects due to this static member. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955199#3955199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955199 |