Skip to main content
Jump to: navigation, search



For @Cache, the existence option should still be allowed when not using a shared cache. Also its default in JPA is check-database.

The default cache size is 100. 14:19, 21 July 2008 (EDT)

Will move existence checking out of the check box-enabled panel

The default for existence checking says CHECK_CACHE in the ExistenceChecking annotation. In org.eclipse.persistence.queries.DoesExistQuery the existencePolicy is set to CHECK_CACHE in the constructor, so that also looks to be the default if no ExistenceChecking annotation is used.

Yes, the @Cache annotation has the default size set to 100. The problem with this is how do you reconcile that with the persistence unit properties eclipselink.cache.size.default being 1000? I had asked about this internally, but never entered a bug, should I? 21:05, 21 July 2008 (EDT)

Yes, this is kind of confusing. The default existence in EclipseLink native API is check-cache, the default for JPA is check-database. It is set in MetadataDescriptor. The default for the annotation if the enum is not set is check-cache.

The cache size is also screwy. The comment that says the default is 1000 is wrong, this may have been the case for TopLink Essentials before the @Cache annotation existed, but is no longer the case. The default is 100. If the persistence unit cache property is set, if overrides the @Cache setting, even if the persistence unit default is set it will override, which seems very odd, and should probably be fixed. Feel free to log a bug for this and the size comment, if there isn't one already. 09:34, 22 July 2008 (EDT)

Will update the existence checking defaults in the spec. Updated docs bug 239134 to make sure the EclispeLink docs explain the default.

bug 231843 was entered for the persistence unit cache defaults overriding the annotation. I updated the EclipseLink docs with the default of 100 and entered bug 241851 to update the JavaDocs in PersistenceUnitProperties 14:18, 23 July 2008 (EDT)

Back to the top