Is there a specific reason why do you want to do that? Because, the first time you access the object, it will be created and stored in cache
________________________________ From: Anindya Mukherjee [mailto:anindya.mukher...@gmail.com] Sent: Wednesday, July 15, 2009 3:28 PM To: user-java@ibatis.apache.org Subject: RE: Force cache refresh + precaching Hi Vinaya, Thanks a lot for the help. I actually meant during app load ( when our application is booting ). - Anindya From: Vinaya Tirikkovalluru [mailto:vinaya.tirikkovall...@converge.com] Sent: July-16-09 12:41 AM To: user-java@ibatis.apache.org Subject: RE: Force cache refresh + precaching Hi, What do you mean by before app load? To forcefully refresh the cache, you can use getSqlMapClient().flushDataCache("sqlmap.queryname"); Vinaya ________________________________ From: Anindya Mukherjee [mailto:anindya.mukher...@gmail.com] Sent: Wednesday, July 15, 2009 3:06 PM To: user-java@ibatis.apache.org Cc: anindya.mukher...@gmail.com Subject: Force cache refresh + precaching Hi , We have started using iBatis caches. To start with we are using an LRU cache. However we have an issue , the underlying tables in our db can be updated by manual inserts ( it is a shared db used by a number of apps ). Now we need a mechanism whereby we can forcefully refresh the iBatis cache. Can anybody help us with this ? Also the ibatis caches are lazy loading ( it loads on demand ) , is it possible to somehow precache some data during app load. - Thanks, - Anindya ________________________________ This electronic message is intended only for the use of the individual(s) or entity(ies) named above and may contain information which is privileged and/or confidential. If you are not the intended recipient, be aware that any disclosure, copying, distribution, dissemination or use of the contents of this message is prohibited. If you received this message in error, please notify the sender immediately. This electronic message is intended only for the use of the individual(s) or entity(ies) named above and may contain information which is privileged and/or confidential. If you are not the intended recipient, be aware that any disclosure, copying, distribution, dissemination or use of the contents of this message is prohibited. If you received this message in error, please notify the sender immediately.
