ppalaga commented on code in PR #4323: URL: https://github.com/apache/camel-quarkus/pull/4323#discussion_r1042064796
########## extensions/jms/runtime/src/main/doc/usage.adoc: ########## @@ -7,3 +7,29 @@ you must ensure that the `camel-quarkus-xml-jaxp` extension is present on the cl When sending JMS message payloads as `javax.jms.ObjectMessage`, you must annotate the relevant classes to be registered for serialization with `@RegisterForReflection(serialization = true)`. Note that this extension automatically sets `quarkus.camel.native.reflection.serialization-enabled = true` for you. Refer to the xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information. + +=== Pooling and XA integrate support + +You can use the `quarkus-pooled-jms` extension to get pooling and XA integrate support for JMS connections. Refer to the https://quarkiverse.github.io/quarkiverse-docs/quarkus-pooled-jms/dev/index.html[quarkus-pooled-jms] extension documentation for more information. Currently, it only works with `quarkus-artemis-jms` extension. Just add these two dependencies to your `pom.xml`: +[source,xml] +---- +<dependency> + <groupId>io.quarkiverse.messaginghub</groupId> + <artifactId>quarkus-pooled-jms</artifactId> +</dependency> +<dependency> + <groupId>io.quarkiverse.artemis</groupId> + <artifactId>quarkus-artemis-jms</artifactId> +</dependency> +---- + +Pooling is default enabled and for XA integrate support, you need to add the following configuration to your `application.properties`: Review Comment: ```suggestion Note that pooling is enabled by default. To enable XA, you need to add the following configuration to your `application.properties`: ``` ########## extensions/jms/runtime/src/main/doc/usage.adoc: ########## @@ -7,3 +7,29 @@ you must ensure that the `camel-quarkus-xml-jaxp` extension is present on the cl When sending JMS message payloads as `javax.jms.ObjectMessage`, you must annotate the relevant classes to be registered for serialization with `@RegisterForReflection(serialization = true)`. Note that this extension automatically sets `quarkus.camel.native.reflection.serialization-enabled = true` for you. Refer to the xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information. + +=== Pooling and XA integrate support + +You can use the `quarkus-pooled-jms` extension to get pooling and XA integrate support for JMS connections. Refer to the https://quarkiverse.github.io/quarkiverse-docs/quarkus-pooled-jms/dev/index.html[quarkus-pooled-jms] extension documentation for more information. Currently, it only works with `quarkus-artemis-jms` extension. Just add these two dependencies to your `pom.xml`: Review Comment: ```suggestion You can use the `quarkus-pooled-jms` extension to get pooling and XA support for JMS connections. Refer to the https://quarkiverse.github.io/quarkiverse-docs/quarkus-pooled-jms/dev/index.html[quarkus-pooled-jms] extension documentation for more information. Currently, it only works with `quarkus-artemis-jms` extension. Just add these two dependencies to your `pom.xml`: ``` Side note: Single sentence per line makes the reviews and future changes easier to track. ########## extensions/jms/runtime/src/main/doc/usage.adoc: ########## @@ -7,3 +7,29 @@ you must ensure that the `camel-quarkus-xml-jaxp` extension is present on the cl When sending JMS message payloads as `javax.jms.ObjectMessage`, you must annotate the relevant classes to be registered for serialization with `@RegisterForReflection(serialization = true)`. Note that this extension automatically sets `quarkus.camel.native.reflection.serialization-enabled = true` for you. Refer to the xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information. + +=== Pooling and XA integrate support Review Comment: ```suggestion === Support for Connection pooling and X/Open XA distributed transactions ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
