Customize concurrency at listener level

Prior to this commit, customizing the concurrency to use fo a given JMS
listener involved to define it in a specific listener-container. As
this is quite restrictive, users may stop using the XML namespace
support altogether to fallback on regular abstract bean definition for
the container.

This commit adds a concurrency attribute to the jms and jca listener
element as well as on the @JmsListener annotation. If the value is set,
it takes precedence; otherwise the value provided by the factory is
used.

Issue: SPR-11988
This commit is contained in:
Stephane Nicoll
2014-07-14 15:49:05 +02:00
parent 5e1a5c8d51
commit 29bdbceaa2
14 changed files with 140 additions and 9 deletions

View File

@@ -41661,6 +41661,12 @@ describes all available attributes:
| selector
| An optional message selector for this listener.
| concurrency
| The number of concurrent sessions/consumers to start for this listener. Can either be
| a simple number indicating the maximum number (e.g. "5") or a range indicating the lower
| as well as the upper limit (e.g. "3-5"). Note that a specified minimum is just a hint
| and might be ignored at runtime. Default is the value provided by the container
|===
The `<listener-container/>` element also accepts several optional attributes. This