You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@grails.apache.org by "ClemensSchneider (via GitHub)" <gi...@apache.org> on 2025/04/17 16:36:34 UTC

[I] @CacheEvict used to support an array of cache-names as value which is no longer possible [grails-core]

ClemensSchneider opened a new issue, #14168:
URL: https://github.com/apache/grails-core/issues/14168

   If an invocation of a method results in multiple caches to be cleared, the following was possible using v`1.1.8` of this plugin.
   
   `@CacheEvict(value=[StatisticsService.SERVICE_STATISTICS_CACHE, StatisticsService.DETAILED_TRANSFER_STATISTICS_CACHE, StatisticsService.GENERAL_STATISTICS_CACHE], allEntries=true)`
   
   Now it's throwing an exception as the `cacheNameException` is being cast to an `ConstantExpression` (`ConstantExpression cacheNameExpression = (ConstantExpression)ScriptBytecodeAdapter.castToType(annotationNode.getMember("value"), ConstantExpression.class);`)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@grails.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org