TransactionOption.Required and SOAP

[John Wood]

Can someone confirm that TransactionOption.Required isn't supported for
webservices... I thought all webservices can only act as the root of a
transaction and not join an existing transaction, because of the stateless
nature of HTTP?

If that's true, then what is this article going on about:
http://www.codeguru.com/Csharp/Cshar....php/c7789__3/

Thanks,
John

[Scott Allen]

Hi John:

TransactionOption.Required is a valid option for a web service method.

The second half of your statement is correct, a web method has to be a
root. In this case, Required and RequiresNew will behave identically,
because when the runtime sees Transaction.Required it will create a
new transaction for the method.

That's the current behavior, as WS-Transaction and other WS-* specs
should will have an impact in the future.

--
Scott
http://www.OdeToCode.com/

On Mon, 11 Oct 2004 12:06:21 -0400, "John Wood"
<john.wood@priorganize_nospam__.com> wrote:

Can someone confirm that TransactionOption.Required isn't supported for
webservices... I thought all webservices can only act as the root of a
transaction and not join an existing transaction, because of the stateless
nature of HTTP?

If that's true, then what is this article going on about:
http://www.codeguru.com/Csharp/Cshar....php/c7789__3/

Thanks,
John

[John Wood]

Thanks for your clarification.
Do you happen to know if Indigo supports distributed transactions between
SOAP calls?

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:n6********************************@4ax.com...

Hi John:

TransactionOption.Required is a valid option for a web service method.

The second half of your statement is correct, a web method has to be a
root. In this case, Required and RequiresNew will behave identically,
because when the runtime sees Transaction.Required it will create a
new transaction for the method.

That's the current behavior, as WS-Transaction and other WS-* specs
should will have an impact in the future.

--
Scott
http://www.OdeToCode.com/

On Mon, 11 Oct 2004 12:06:21 -0400, "John Wood"
<john.wood@priorganize_nospam__.com> wrote:

Can someone confirm that TransactionOption.Required isn't supported for
webservices... I thought all webservices can only act as the root of a
transaction and not join an existing transaction, because of the statelessnature of HTTP?

If that's true, then what is this article going on about:

http://www.codeguru.com/Csharp/Cshar...article.php/c7

789__3/

Thanks,
John

[Scott Allen]

Yes, that's the current plan I've heard. Indigo will support the WS
security, transaction, reliable messaging, addressing, and policy
specifications when it arrives. The only questions is when.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 11 Oct 2004 14:18:19 -0400, "John Wood"
<john.wood@priorganize_nospam__.com> wrote:

Thanks for your clarification.
Do you happen to know if Indigo supports distributed transactions between
SOAP calls?

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:n6********************************@4ax.com.. .

Hi John:

TransactionOption.Required is a valid option for a web service method.

The second half of your statement is correct, a web method has to be a
root. In this case, Required and RequiresNew will behave identically,
because when the runtime sees Transaction.Required it will create a
new transaction for the method.

That's the current behavior, as WS-Transaction and other WS-* specs
should will have an impact in the future.

--
Scott
http://www.OdeToCode.com/

On Mon, 11 Oct 2004 12:06:21 -0400, "John Wood"
<john.wood@priorganize_nospam__.com> wrote:

>Can someone confirm that TransactionOption.Required isn't supported for
>webservices... I thought all webservices can only act as the root of a
>transaction and not join an existing transaction, because of thestateless >nature of HTTP?
>
>If that's true, then what is this article going on about:

http://www.codeguru.com/Csharp/Cshar...article.php/c7

789__3/

>
>Thanks,
>John
>