I am using the Spring Framework to configure all of my business objects, including an instance of TreeCache (rather than using MBeans). I was hoping to be able to create a CacheLoader bean in my Spring configuration xml file which I can set as the CacheLoader property on the TreeCache.
This approach sort of works (the CacheLoader gets set properly, and the CacheLoaderIntercepter properly delegates the get methods to my class), however TreeCache doesn't initialize my loader. Specifically, it doesn't call setConfig(), setCache(), create(), or start(). I don't have a problem with it not calling setConfig() or create() (these should probably only be called when the CacheLoader is created and configured by TreeCache), but it seems like it should always call setCache() on the CacheLoader, and it should probably call start() in notifyCacheStarted() or in startService(). I have a feeling the intention was to always provide CacheLoaderClass and CacheLoaderConfig, but in my case, it is much more convenient to pass in an already created/configured CacheLoader, and still have TreeCache behave properly. I can provide a patch for how I think it should behave, but wanted to get color on why it behaves the way it does now. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872934#3872934 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872934 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
