Charlie
My feedback
137 results found
-
43 votesCharlie supported this idea ·
-
51 votesCharlie supported this idea ·
-
19 votesCharlie supported this idea ·
-
73 votesCharlie supported this idea ·
-
21 votesCharlie supported this idea ·
-
37 votesCharlie supported this idea ·
-
61 votesCharlie supported this idea ·
-
33 votesCharlie supported this idea ·
-
456 votesCharlie supported this idea ·
-
4 votesCharlie supported this idea ·
-
4 votesCharlie supported this idea ·
-
10 votesCharlie supported this idea ·
-
16 votesCharlie supported this idea ·
-
49 votes
An error occurred while saving the comment -
4 votesCharlie supported this idea ·
-
150 votesCharlie supported this idea ·
-
9 votesCharlie supported this idea ·
You can actually do this already if the other resource(s) are XA aware. You just have to prepare on the XA resource(s) (no prepare for Mongo), then commit mongo first and, if successful, commit the XA transaction. So the XA transaction wraps the single non-XA resource between the XA prepare and XA commit.