-
October 3rd, 2012, 02:52 AM
#1
webservices to replace com+ objects
I have some old code using com+ transactions (I think they call it "contexts"). I know have to replace these old modules with a number of webservices. What would be the best choice of technology to handle these contexts today? I don't believe I can make a sql transaction that works between webservices, but I need something like it.
Any good suggestions?
Edit: I saw something about System.Enterpriseservices - is that the way to go?
Can I do something like:
Main program:
Start "transaction"
Call WS1
Call WS2
Wait for both webservices to complete
Commit/Rollback "transaction" depending on whether it went good or bad
WS1:
Begin local transaction
do work
Commit/Rollback local transaction
return ok or fail
WS2:
Begin local transaction
do work
Commit/Rollback local transaction
return ok or fail
Last edited by Lars_V_J; October 3rd, 2012 at 03:04 AM.
-
October 12th, 2012, 08:11 AM
#2
Re: webservices to replace com+ objects
See:
http://msdn.microsoft.com/en-us/library/ms254973.aspx
Microsoft article on .Net Distributed Transactions
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|