Merge Messaging Meta-Annotation Attributes [INT-3376]

[spring-operator]

Gary Russell opened INT-3376 and commented

When using messaging meta-annotations (e.g. @MyServiceActivator annotated with @ServiceActivator) the framework currently only considers attrbutes (input-channel etc) on the framework annotation.

To provide increased flexibility, we should consider that attributes with the same name on the user annotation should supplement/override those on the framework annotation.

This would allow the user annotation to specify common attributes with each individual use of that annotation supply attributes such as input-channel.

---

Issue Links:

• Add support for @BridgeFrom and @BridgeTo MessageChannel @Bean level annotations for @Configuration classes [INT-3380] #7351 Add support for @BridgeFrom and @BridgeTo MessageChannel @Bean level annotations for @Configuration classes
  ("is depended on by")

• Allow to configure Messaging Annotations (@ServiceActivator, @InboundChannelAdapter etc.) on @Bean method level for MessagaSource<?>, MessageHandler components (e.g. FileReadingMessageSource) [INT-3381] #7352 Allow to configure Messaging Annotations (@ServiceActivator, @InboundChannelAdapter etc.) on @Bean method level for MessagaSource<?>, MessageHandler components (e.g. FileReadingMessageSource)
  ("is depended on by")

• SPR-11709 Consider not overriding meta-annotation attributes if empty

• SPR-11711 Introduce isAnnotation() in ClassMetadata API

Referenced from: pull request #1132

1 votes, 2 watchers