I was just trying to explore other options that might be simpler in terms of the configuration. At some point (once we have a GA version available, planned for Spring Integration 2.1), you might want to consider our AMQP integration.
In the meantime, the way you are describing it might handle it fine. Another option I would consider is simply referencing a "task-executor" within the <poller> element. Then, you could have a number of different, reusable thread pool configurations. For example, you might have "high", "medium", and "low" priority (where priority is handled by the number of threads). Then you would be able to use "highPriorityExecutor" everywhere you need that one.