Originally JCache was meant to be included in the Java EE spec canon. When working on a next version of JCache that requirement is probably one of the "most wanted". Looking at the efforts so far I see a major conceptual problem:
a) The JCache spec says that the cache configuration is outside of the spec
b) An EE application should run on an EE server. If the application uses JCache for caching, there must be enough configuration information that is independent of the cache vendor to run the application
Solutions variants I can think of at the moment:
no extra configuration. specify that a default cache should hold at least 1000 elements.
standard configuration file that enlists the used caches in the application and parameters that are known in the JCache configuration object. Also it contains a description of the intended use, so an admin can configure a specific implementation properly.
instead of naming the caches, introduce labels. this should allow the admin to set a vendor specific cache configuration of a group of caches with the same label.
Originally JCache was meant to be included in the Java EE spec canon. When working on a next version of JCache that requirement is probably one of the "most wanted". Looking at the efforts so far I see a major conceptual problem:
a) The JCache spec says that the cache configuration is outside of the spec b) An EE application should run on an EE server. If the application uses JCache for caching, there must be enough configuration information that is independent of the cache vendor to run the application
Solutions variants I can think of at the moment: