Project

General

Profile

« Previous | Next » 

Revision 4b2b6fc7

Added by Andreas Müller almost 4 years ago

rename CdmCacher to CdmCacherBase

View differences:

cdmlib-services/src/main/java/eu/etaxonomy/cdm/api/service/IService.java
132 132 
     * <p>
133 133 
     * <b>WARNING:</b>This method should <em>ONLY</em> be used when it is absolutely
134 134 
     * necessary and safe to ensure that the hibernate session is not flushed before a read
135 
     * query. A use case for this is the {@link eu.etaxonomy.cdm.api.cache.CdmCacher CdmCacher},
136 
     * (ticket #4276) where a call to {@link eu.etaxonomy.cdm.api.cache.CdmCacher#load(UUID) load}
135 
     * query. A use case for this is the {@link eu.etaxonomy.cdm.api.cache.CdmCacherBase CdmCacher},
136 
     * (ticket #4276) where a call to {@link eu.etaxonomy.cdm.api.cache.CdmCacherBase#load(UUID) load}
137 137 
     * the CDM Entity using the standard {@link #find(UUID) find} method results in recursion
138 138 
     * due to the fact that the {@link #find(UUID) find} method triggers a hibernate session
139 139 
     * flush which eventually could call {@link eu.etaxonomy.cdm.model.name.NonViralName#getNameCache getNameCache},
140 140 
	 * which in turn (in the event that name cache is null) eventually calls the
141 
	 * {@link eu.etaxonomy.cdm.api.cache.CdmCacher#load(UUID uuid) load} again.
141 
	 * {@link eu.etaxonomy.cdm.api.cache.CdmCacherBase#load(UUID uuid) load} again.
142 142 
	 * Apart from these kind of exceptional circumstances, the standard {@link #find(UUID) find}
143 143 
	 * method should always be used to ensure that the persistence layer is always in sync with the
144 144 
	 * underlying database.

Also available in: Unified diff