In grouper 2.3.0 (unpatched) and previous versions, ehcache was configured with an ehcache.xml (actually in old versions of grouper there were a couple ehcache xml config files).
Sample ehcache.xml config
<cache name="edu.internet2.middleware.grouper.internal.dao.hib3.Hib3MemberDAO.FindBySubject" maxElementsInMemory="5000" eternal="false" timeToIdleSeconds="5" timeToLiveSeconds="10" overflowToDisk="false" statistics="false" /> |
This needs to be converted to config overlays so Grouper packaging can have defaults and overlays. Also so the Grouper team can add caches and be able to patch the defaults without having to merge with a potentially changed file.
Sample grouper.cache.base.properties config:
cache.name.internal_dao_hib3_Hib3GroupDAO.name = edu.internet2.middleware.grouper.internal.dao.hib3.Hib3GroupDAO cache.name.internal_dao_hib3_Hib3GroupDAO.maxElementsInMemory = 500 cache.name.internal_dao_hib3_Hib3GroupDAO.eternal = false cache.name.internal_dao_hib3_Hib3GroupDAO.timeToIdleSeconds = 1 cache.name.internal_dao_hib3_Hib3GroupDAO.timeToLiveSeconds = 1 cache.name.internal_dao_hib3_Hib3GroupDAO.overflowToDisk = false |
Note, the part that links the properties entries together is the part between "name" and the following dot. In this case "internal_dao_hib3_Hib3GroupDAO". This was automatically converted from the ehcache.xml file by looking at the cache name and chopping off the prefix "edu.internet2.middleware.grouper", though thats not important, it could be "abc" and it would work. However, we should follow this convention going forward.
If you upgrade to 2.3.1+ it will walk you through the process of automatically converting your ehcache.xml to grouper.cache.properties
sdf