INT-3567: JMS Shared Subscriptions

JIRA: https://jira.spring.io/browse/INT-3567

Namespace support for JMS 2.0 shared subscriptions.

INT-3567: AsciiDoc

* `What's New` polishing
* `TcpConnectionEventInboundChannelAdapterParser` deprecation warn fix

src/reference/asciidoc/jms.adoc

@@ -106,6 +106,11 @@ When comparing this to the generic gateway configuration, or the JMS 'inbound-ga
 Therefore, the flow downstream from the 'error-channel' should also be one-way.
 For example, it could simply send to a logging handler, or it could be connected to a different JMS <outbound-channel-adapter> element.
 
+When consuming from topics, set the `pub-sub-domain` attribute to true; set `subscription-durable` to true
+for a durable subscription, `subscription-shared` for a shared subscription (requires a JMS 2.0 broker and
+has been available since _version 4.2_).
+Use `subscription-name` to name the subscription.
+
 [[jms-md-conversion-errors]]
 ==== Inbound Conversion Errors
 [NOTE]
@@ -196,6 +201,11 @@ The same idea applies here: The _exceptionTransformer_ could be a simple POJO th
 
 NOTE: See <<jms-md-conversion-errors>>.
 
+When consuming from topics, set the `pub-sub-domain` attribute to true; set `subscription-durable` to true
+for a durable subscription, `subscription-shared` for a shared subscription (requires a JMS 2.0 broker and
+has been available since _version 4.2_).
+Use `subscription-name` to name the subscription.
+
 [[jms-outbound-gateway]]
 === Outbound Gateway
 
@@ -494,6 +504,11 @@ The example below provides both a custom instance for resolution of the JMS Dest
     connection-factory="customConnectionFactory"/>
 ----
 
+For the `<publish-subscribe-channel />`; set the `durable` attribute to true
+for a durable subscription, `subscription-shared` for a shared subscription (requires a JMS 2.0 broker and
+has been available since _version 4.2_).
+Use `subscription` to name the subscription.
+
 [[jms-selectors]]
 === Using JMS Message Selectors
 

src/reference/asciidoc/whats-new.adoc

@@ -155,9 +155,19 @@ Of course, Reactor is still supported for functionality such as the `Promise` ga
 [[x4.2-jms-changes]]
 ==== JMS Changes
 
+===== Conversion Errors in Message-Driven Endpoints
+
 The `error-channel` now is used for the conversion errors, which have caused a transaction rollback and message redelivery previously.
 
-See <<jms-message-driven-channel-adapter>> for more information.
+See <<jms-message-driven-channel-adapter>> and <<jms-inbound-gateway>> for more information.
+
+===== Shared Subscriptions
+
+Namespace support for shared subscriptions (JMS 2.0) has been added to message-driven endpoints and the
+`<int-jms:publish-subscribe-channel>`.
+Previously, you had to wire up listener containers as `<bean/>` s to use shared connections.
+
+See <<jms>> for more information.
 
 [[x4.2-conditional-pollers]]
 ==== Conditional Pollers
@@ -194,7 +204,7 @@ See <<cors>> for more information.
 ==== Persistent File List Filter Changes
 
 The `AbstractPersistentFileListFilter` has a new property `flushOnUpdate` which, when set to true, will `flush()` the
-metadata store if it implements `Flushable` (e.g. the `PropertiesPersistenMetadataStore`).
+metadata store if it implements `Flushable` (e.g. the `PropertiesPersistingMetadataStore`).
 
 
 [[x4.2-gw]]
@@ -223,7 +233,7 @@ Currently, JDBC, Redis and MongoDB message stores support this property.
 
 ===== Output MessageGroupProcessor
 
-When using a `ref` or innner bean for the aggregator, it is now possible to bind a `MessageGroupProcessor` directly.
+When using a `ref` or inner bean for the aggregator, it is now possible to bind a `MessageGroupProcessor` directly.
 In addition, a `SimpleMessageGroupProcessor` is provided that simply returns the collection of messages in the group.
 When an output processor produces a collection of `Message<?>`, the aggregator releases those messages individually.
 Configuring the `SimpleMessageGroupProcessor` makes the aggregator a message barrier, were messages are held up