Transaction for Webservice in dotnet

Question

0.00/5 (No votes)

See more:

HI is there any mechanism which can handle situation like this

''' if i have one web service with 3 methods in it say
UpdateTbl,InsertTbl,DeleteTbl web methods

if i am calling these methods from client To Run them

like this
First UpdateTbl method which performs some operation in database
Second InsertTbl method which performs some operation on same database of above
Third DeleteTbl method which performs some operation on same database of Above

now can i set at client side that
iF any of the above method fails with exception i should get all my database operations to rollback to state which was before calling first method ??

please help us with your valuable suggestions

Posted 8-May-11 21:52pm

kakani santosh kumar

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CDP1802 · Answer 1 · 2011-05-08T22:15:00

A webservice is stateless and therefore not well suited to handle such things from the client side. The webservice can hold a session state which you might use for that, but this still would be a hack.

The real problem is, that the client side (which is the presentation layer) should not have any knowledge or control over transactions on the server (the application logic). This is a question of proper application design and when a layer (in this case the client) needs to know about another layer's internal state, then there is something wrong with the design.

Let's assume you have the following methods:

GetUser(), UpdateUser(), UpdateActiveUserList()

You might call them whenever a user logs in, but three separate calls would not be in a transaction. So why don't you implement a new web method UserLogin() which internally uses all three methods in a transaction? Then the server 'knows' how to handle this and the client must not care about details like transactons anymore. And, of course, expose only those methods as web methods which the client really needs, no more and no less.