Spring Operator
Spring Operator
**[Mark Fisher](https://jira.spring.io/secure/ViewProfile.jspa?name=mark.fisher)** commented I don't think it would be a good idea to make a bunch of channels appear to be one channel. That is blurring the distinction between the...
**[Oleg Zhurakousky](https://jira.spring.io/secure/[email protected])** commented For multi-channel router I agree, its already a _multi-channel router_, so we just need to make sure it recognizes patterns. The way I interpreted the requirement was...
**[Mark Fisher](https://jira.spring.io/secure/ViewProfile.jspa?name=mark.fisher)** commented I think using the name pattern in the output-channel is something we want to avoid. That really starts to blur the line between a router and channel....
**[Oleg Zhurakousky](https://jira.spring.io/secure/[email protected])** commented I agree and I think i misinterpreted the requirement and was trying to find justification for _output-channel=""_ Multi-channel router which recognizes pattern is a much cleaner solution
**[Mark Fisher](https://jira.spring.io/secure/ViewProfile.jspa?name=mark.fisher)** commented moving to RC1 for now, but we might consider postponing until after 2.0.0
**[Mark Fisher](https://jira.spring.io/secure/ViewProfile.jspa?name=mark.fisher)** commented On second thought, I think we might want to be careful with this one. Perhaps we can provide this feature in "recipient-list-router" or some other focused component....
**[Mark Fisher](https://jira.spring.io/secure/ViewProfile.jspa?name=mark.fisher)** commented Moving to 2.1.
**[Oleg Zhurakousky](https://jira.spring.io/secure/[email protected])** commented Although it sounds simple there are many ways to approach it and finding the most appropriate is what makes it tricky, so we'll revisit this in 2.2
**[Gary Russell](https://jira.spring.io/secure/ViewProfile.jspa?name=grussell)** commented Perhaps the advice can have a property `lockKeyExpression` (used to determine which lock to acquire). Also, an optional `discardChannel`, used when the `lockKeyExpression` returns `null`.
**[Artem Bilan](https://jira.spring.io/secure/ViewProfile.jspa?name=abilan)** commented Looks like we should just provide `PayloadValidatingMessageSelector` implementation based on the `org.springframework.validation.Validator` abstraction, which, in turn, provides the JSR 303 wrapper: https://docs.spring.io/spring/docs/5.0.0.RC4/spring-framework-reference/core.html#validation