John Blum

For one such example of an extension outside the _spring-cloud-bindings_ project itself, see [here](https://github.com/spring-projects/spring-boot-data-geode/blob/master/spring-geode-cloud/src/main/java/org/springframework/geode/cloud/bindings/boot/GeodeBindingsPropertiesProcessor.java).

Hi @NerminKarapandzic - Thank you for your interests and submitting a request on this topic. I don't think this is the first time users have requested functionality, similar to what...

Hi @NerminKarapandzic - We try to make it as easy for our awesome community, like yourself, as possible to contribute to any Spring project, including Spring Data Redis. We have...

Thank you @NerminKarapandzic. My advice would be to maybe start with just a simple prototype at first, a test and maybe an example, that would answer the question, "_What would...

Thank you so much @NerminKarapandzic! Really appreciate this. I will have a look in a few days. Currently, involved in few other activities that need my quick attention. Will get...

Hi @NerminKarapandzic - Sorry for the delayed response. No, sorry. This ticket is not deemed high priority at the moment, and needs better cross-project coordination (Spring Integration and Spring Cloud...

I created the [topic/issue branch](https://github.com/spring-projects/spring-data-redis/tree/issue/2484) with my changes to date; more editing to do yet.

The only reason I set the value to a "`Ex`" in `KeyExpirationEventMessageListener` is to preserve existing behavior in the `3.x` line. In `4.0`, I think this should also be set...

@christophstrobl - Thank you for your feedback. Correct me if I am wrong, but it seems that 1) the `RedisKeyValueAdapter.MessageExpirationListener` [extends](https://github.com/spring-projects/spring-data-redis/blob/issue/2670/src/main/java/org/springframework/data/redis/core/RedisKeyValueAdapter.java#L760) from the SD Redis `KeyExpirationEventMessageListener` class directly where [I...

@christophstrobl - I understood your concern and your point. I was also trying to explain that we are not really changing behavior here since we are still receiving "expiration" events...