Hi Rodrigo,
Well, I'm thinking that if your requirements are such that your application
cannot tolerate an eventual consistency of such a level then probably a
more "traditional" XA type of solution would be more appropriate for your
circumstances.
HTH,
Savvas
On 8 June 2015 at 19:02, Rodrigo U
Guys,
Once again, thank you both for your help.
Savvas, that's really an option we're considering. But like Michael said,
it would be just a workaround, not really an "atomic transaction". But it
is indeed one option. I'm still trying to weight which of the two pays off.
Regards,
Rodrigo.
On Mo
I am not sure this will always be the best solution if the inserts at
the two servers need to be treated as a single business operation.
The solution you propose means that the inserts do not happen atomically
and therfore you will put Consistency and Isolation at risk - ie other
applications
Hi Rodrigo,
Does this really have to be in the classical sense of a "distributed
transaction"? Can you not have App B embed a "undo" hypermedia link in its
response?
Given the following steps:
1) App A starts transaction and inserts some rows
2) App A makes REST call to app B
3) App B inserts ro
REST-AT and JTA are different transaction models. Unfortunately we only
provide an "inbound bridge" to go from REST-AT to JTA but I think you
need the other direction ie JTA to REST-AT.
There may be a workaround for you though which I would need to
experiment with. You would need to start a RE
Mike,
I have been reading the docs and taking a look at the code samples. I'm
still unsure however if the protocol/api covers the scenario I'm in:
I have a client web app (A), and a REST endpoint (B). Two separate
applications. Client in web app A is not a REST endpoint itself, just a
regular sta
Thanks a lot, Mike! Exactly what I needed.
On Tue, May 26, 2015 at 6:06 AM, Michael Musgrove
wrote:
> The narayana transaction manager has a rest service that creates
> [transaction] Coordinator resources. These resources map onto conventional
> ACID transactions. It is up to your service to de
The narayana transaction manager has a rest service that creates
[transaction] Coordinator resources. These resources map onto
conventional ACID transactions. It is up to your service to decide what
to do when the "transaction" is completing. However, we also have a "JTA
Bridge" that will detec
I have an web application "A" that occasionally have to insert/update
records that belong to another application, "B". To manage this
requirement, application "B" expose some REST endpoints that application
"A" will call whenever it needs.
Problem is, we need to make sure that the inserts/updates
