Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 3.00, 3.01, 3.02, 3.03, 3.04, 3.05, 3.06, 3.07, 3.08, 3.09, 3.10, 3.11, 3.12, 3.13, 3.14, 3.15, 3.16
-
Fix Version/s: 3.17
-
Component/s: Referencing
-
Labels:
Description
CachedAuthorityFactory performs its cache using the authority code as keys. It was sufficient as long as the risk of having the same code used by two different kind of objects was low. However in latest EPSG databases, such clashes occur more often. It does not compromise the validity of the created CRS, however it causes CachedAuthorityFactory to discard and recreate objects more often than necessary.
A beneficial side effect of this work would be to get ride of the need for the Cache.setKeyCollisionAllowed(true) method.
On a related note (
GEOTK-61), we may also revisit the policy of not using the cache during IdentifiedObjectFinder operations.GEOTK-61), we may also revisit the policy of not using the cache during IdentifiedObjectFinder operations.