[ https://jira.jboss.org/jira/browse/ISPN-333?page=com.atlassian.jira.plugi... ] Manik Surtani resolved ISPN-333. -------------------------------- Resolution: Rejected -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-333?page=com.atlassian.jira.plugi... ] Amin Abbaspour commented on ISPN-333: ------------------------------------- There problem still exists for me, but I did not re-open since I was afraid this is a problem in my side and commented in related forum post. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-333?page=com.atlassian.jira.plugi... ] Manik Surtani updated ISPN-333: ------------------------------- Workaround Description: Configure your cache programmatically Fix Version/s: 4.1.0.ALPHA1 4.1.0.GA Complexity: Low Workaround: [Workaround Exists] "Aha, I see the problem. Note that this only happens if you construct a CacheManager using an XML file or InputStream, which is why it never turned up in my tests (I used a GlobalConfiguration and Configuration bean, configured programmatically). The issue is that each CacheStore impl has a corresponding CacheStoreConfig impl, which has knowledge of settings specific to the CacheStore impl in question. When configuring stuff programmatically, you simply create a new instance of the CacheStoreConfig impl and pass it to the Configuration (e.g., a new FileCacheStoreConfig). But when you do this via XML, all CacheStore settings are maintained using <property ... /> tags. So we need to know what type of CacheStoreConfig to instantiate and pass these properties to. And the mechanism currently in place to do this is to instantiate the CacheStore implementation and call CacheStore.getConfigurationClass(). The CacheStore instance is then thrown away since the cache hasn't started yet (this is still at a much earlier phase, of parsing XML). In summary, I will reopen ISPN-333 and investigate how this can be improved, but this is low prio since the first instantiation happens on startup and has no effect or cost to runtime performance." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-333?page=com.atlassian.jira.plugi... ] Manik Surtani resolved ISPN-333. -------------------------------- Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira