waldi5001 commented on code in PR #3999:
URL: https://github.com/apache/activemq-artemis/pull/3999#discussion_r846432151


##########
docs/user-manual/en/resource-adapter.md:
##########
@@ -0,0 +1,130 @@
+# Resource Adapter
+
+For using Apache ActiveMQ Artemis in a JavaEE/JakartaEE environment, you can 
use the ResourceAdapter. Before you 
+start, read carefully the [JMS chapter](using-jms.md) 
+
+##In which case do you have to use a RA and in which not?
+The main reason is the requirement of 
+[XA](https://jakarta.ee/specifications/transactions/2.0/jakarta-transactions-spec-2.0.html),
 distributed 
+transactions over multiple resources. If it is important for you no message 
get lost and multiple resources (e.g. 
+database and messaging) must be in sync, there is no way around it.
+
+##Versions
+let's give you a short overview of the versions, to be sure you pick the 
correct *.rar.
+
+| | artemis-ra-rar   |     |     |
+| --------- | ------ | --- | --- |
+| Artemis   | JavaEE | JCA | JMS |
+| \>= 2.18.0 | \>=8      | 1.7 | 2.0 |
+| <= 2.17.0 | 7      | 1.5 | 2.0 |
+
+| | artemis-jakarta-ra-rar | | |
+| --- | ------- | --- | --- |
+| Artemis | JavaEE | JCA | JMS |
+| \>= 2.18.0 | \>=9 | 2.0 | 3.0 |
+
+## Lets start
+To use the RA, you have to build it by your own. This sounds harder than it 
is. But no worries, an 
+[examples](examples.md) 

Review Comment:
   I want to prove you completely right, but if you are looking the diff with 
"ignore whitespace" you can see it well. In my comment of the commit I 
describes the changes:
   * update xml schemas
   * fix ConnectionParameters
   * remove TransactionManagerLocatorMethod and "The producer max rate"
   * remove The max connections
   
   nevertheless: With my next commit I reformat the file, and I hope the diff 
will become more readable.



-- 
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]

Reply via email to