Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception cache resolver shouldn't be mandatory [SPR-12850] #17448

Closed
spring-issuemaster opened this issue Mar 25, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

commented Mar 25, 2015

Stéphane Nicoll opened SPR-12850 and commented

The caching abstraction provides various ways of configuring the component responsible of retrieving the cache at runtime.

CachingConfigurer was the main interface and an extra interface was created when the abstraction runs with JSR-107 support JCacheConfigurer

JCache has the notion of an exception resolver that can be different from the main one.

Use case:

  1. you don't use JSR-107 at all and you define a CacheResolver via an implementation of CachingConfigurer. All work fine.
  2. You add the JCache API in your classpath, your app breaks because an exception CacheResolver is required and not found

Two potential solutions:

  1. Use the "main" CacheResolver if no specific one has been set
  2. Lazy check for the exception cache resolver (after all you only need this if an exceptionCacheName attribute has been set on a JSR-107 annotation.

Using 1 is probably the easier but I can't recall why it wasn't done initially.


Affects: 4.1 GA

Referenced from: commits 314b069, 073c176, 7aa3175, 5f6ae13, a7fec6a

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented Mar 25, 2015

Stéphane Nicoll commented

Fix applied on master, pending review before the backport to 4.1.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.