How do business logic written in web services manage transactions?

baby_snake

When working on a project recently, the core business logic of a workflow system was implemented using web services.
The goal is to reuse this logic in several other different applications.
The problem is that this web service cannot be managed as a sub-transaction of the calling application.
In other words, when an error occurs in the business after this web service business,
The web service service that has been executed cannot be rolled back.

The appserver we use is websphere
According to some information I surveyed, as far as transaction management of web service business is concerned,
There is currently no standardized technical specification.
And each app server vendor seems to have made their own independent implementation

I would like to invite experts to discuss this issue.

tianfeng

HTTP://MSDN.Microsoft.com/MSDN mag / issues / 06/11 / cutting edge / default.aspx # S6
HTTP://MSDN.Microsoft.com/MSDN mag / issues / 06/11 / cutting edge / default.aspx # S7

pengsuper

mark

pengsuper

Is this problem involved in .net3.0, in wcf

huoensi

mark

xyf1028

This seems to be more difficult indeed. . Consider writing the entire process as a webservice. . And multiple calls to webservice will also affect performance