If you really need them, WCF and MSDTC support WS-AT. However, you should
not even to consider an that option unless there are things outside of your
control that force you to go that way. Generally, you want any transactional
behavior to be hidden behind the service. If your services are being
designed properly, this should not be an issue, since each call will
typically contain all the information to complete the transaction.
I have a post here about how you need to shift your mindset when building
services:
http://www.iserviceoriented.com/blog/post/Introduction+to+Service+Oriented+Architecture.aspxOn Tue, Aug 5, 2008 at 11:11 PM, Hendry Luk <
hendrymail@...> wrote:
> Guys,
> Just curious how do you guys maintain atomic transaction in SOA?
>
> Cheers
> Hendry
>
>
>
