Hello Allan,
Yes, as you've found in the article, XML Webservice naturally does not
support distributed transaction processing. This is due to the loose-couple
between webservice client and server(quite different from other distributed
components such as .net remoting, COM+....).
For your scenario, would you provide us some further background information
of your application(client and server...) and what's the current difficulty
and concerns in the application?
If what you want do is group several webmethod calls into a single
transaction, I think you may consider move the transaction processing from
distributed layer to server-side layer. Here are two possible approaches:
1. Encapsulate all the webmethods into a single webmethod. Thus, we can use
the .net framework's transaction support(System.Transaction namespace in
..net framework 2.0) in that single webmethod to perform transaction
processing in server-side code.
2. Still use separate webmethods to contribute the single transaction
operation, however, instead let the webmethod become a direct unit of the
transaction, we make them a proxy method which will add a record into a
certain transaction queue(defined by ourself). After all those webmethods
has been successfully called, we perform the real transaction process
through another internal method(not expsed as webmethod) to execute all the
transaction operations.
How do you think of the above options? Please feel free to post here if you
have any other ideas or any other information you wonder.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.