Use defaultCache to read default values for 107 unspecified props #32

Open
alexsnaps opened this Issue Nov 4, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@alexsnaps
Member

alexsnaps commented Nov 4, 2014

Based on issue #30, we may want to read things like capacity control (and tiering?) from the defaultCache and merge it in with the Configuration provided to javax.cache.CacheManager#createCache.

Ehcache certainly requires a capacity to be set on the Cache, which now defaults to JCacheManager. DEFAULT_SIZE. There may well be other setting we may want to "copy" from there...

Now I find that capacity set this way seems to only address an implementation issue (i.e. Ehcache requiring this setting), but I don't see how one would actually configure this one single value for all programmatically configured javax.cache.Cache to anything meaningful...

Thoughts?

@ljacomet

This comment has been minimized.

Show comment
Hide comment
@ljacomet

ljacomet Nov 5, 2014

Member

I believe this calls for extending the Configuration or even CompleteConfiguration with our own to add support for the Ehcache specific configurations options.
Now the questions is: to which extent?

  • Everything? if so, we may need a converter from CacheConfiguration to JSR-107 compliant one.
  • Mandatory only? But then what about optional, how do you go about them? Maybe we cover the mandatory needs and defer to using Ehcache API for users having more specific needs with regards to configuration.
Member

ljacomet commented Nov 5, 2014

I believe this calls for extending the Configuration or even CompleteConfiguration with our own to add support for the Ehcache specific configurations options.
Now the questions is: to which extent?

  • Everything? if so, we may need a converter from CacheConfiguration to JSR-107 compliant one.
  • Mandatory only? But then what about optional, how do you go about them? Maybe we cover the mandatory needs and defer to using Ehcache API for users having more specific needs with regards to configuration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment