-
Notifications
You must be signed in to change notification settings - Fork 38.5k
Support @AliasFor for @JmsListener attributes [SPR-13803] #18376
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
Comments
Juergen Hoeller commented I'm not sure there's much we can do about this: According to Java annotation declaration rules, required attributes have to be specified, even when used as meta-annotations. So I suppose that's just a nuisance (having to specify empty String there on the meta-annotation declaration) but the overriding actually works at runtime? Juergen |
Grzegorz Poznachowski commented The thing is that overriding is not working. |
Juergen Hoeller commented On review, I'm afraid that Juergen |
Sam Brannen commented Please note that this issue has been superseded by #18545. |
Sam Brannen commented FYI: this has been addressed in #18545, which is now resolved. For an example of this support in action, consult the following commit: Just search for |
Grzegorz Poznachowski opened SPR-13803 and commented
I want to wrap
@JmsListener
annotation with a custom one (to avoid providing containerFactory attribute):As destination is a required attribute I need to provide its value:
destination = ""
. I would expect that it would be overridden by specifying destination attribute on@CustomJmsListener
, however the@JmsListener
value is being used.Affects: 4.2.3
Issue Links:
@Value
cannot be used as aliased meta-annotation@Cache
* as merged composed annotationsThe text was updated successfully, but these errors were encountered: