By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,404 Members | 2,300 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,404 IT Pros & Developers. It's quick & easy.

Stopping transaction through client in web method

P: n/a
Hi all,
I am having web method which is inserting some heavy data into
database. Everytime client call this method i am generating some unique
transaction.
Client know that transaction ID.

What i want to to provide method to client so that he can rollback that
transaction.

And as soon as client has requested for transaction, transaction should
get rollback.

Can i get list of transactions which are running in web service
currently.

Why i need all this is because some time my web service is giving error
proxy timeout if i am using it througn isa. So if this error occur
client should able to stop currently running tranaction.

Can some one shed some light on it.

Please help me as this is very very imp for me.

Thanks in advnace.

Mar 20 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
What are you using .net 1.x, .net 2.0? with what? wse, wse2, wse3?
wcf?

Mar 22 '06 #2

P: n/a
Hi,

thanks for your reply.

i am using framework 1.1.

can u tell me how to check version of wse?.

thanks in advance.

Mar 22 '06 #3

P: n/a
q
If you didn't install WSE, you're in 1.1. You won't be able to do
fancy transactional stuff in .NET 1.1. I'm 99% sure you need the Web
Service Enhancements to use transaction (the WS-Transactions
specification).

That said, I never really use it... I do it all manually most of the
time by putting together my own XML messages and sending them via a
HttpWebRequest. I do this because 90% of my work involves creating
bridges that access web services and service them as COM+ components.
I find it easier just to do things manually than to bridge the
properties from the WS world to the VB/Navision/COM world.

So, you can either check out the WSE sections of MSDN (I would highly
recommend going to .NET 2.0 first though-- its the difference between
Windows 95 and Windows XP) or you can beef up on your XML and do
everything manually (not really that difficult)

Mar 22 '06 #4

P: n/a
q
That is... you're in 1.1, without WSE.

Mar 22 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.