`@RedisListener` does not resolve property placeholders in all attributes

[yagyesha]

When using the new @RedisListener annotation, the topic attribute does not resolve Spring property placeholders.

For example:

@RedisListener(
id = "myListener",
topic = "${app.my-channel}",
consumes = "application/json"
)
public void handle(String message) {
// ...
}

with:

app.my-channel=my-channel

results in the listener subscribing to the literal Redis channel:

${app.my-channel}

instead of:

my-channel

Is this an expected behavior? or is this a bug/missing feature?

[DragonFSKY]

Hi, I can take a look at this.

I opened #3394 to address the @RedisListener topic/value placeholder resolution reported here.

While working on it, I also noticed a related placeholder-resolution gap that seems separate from this issue: @RedisListener(consumes = "...") currently appears to use the raw annotation value. Unlike id and container, it is not resolved before being set on the listener endpoint, and that value is later used as the synthetic MessageHeaders.CONTENT_TYPE for message conversion. This means a value such as ${app.redis.content-type} would be propagated literally instead of resolving to application/json.

I kept #3394 focused on the @RedisListener topic/value case reported here. If you think this related case is worth addressing too, I can open a separate focused issue/PR with a regression test.