07-01-04 10:53 PM
I believe this should be fine. Your component just will not participate in
the transaction. E.g. any SQL operations performed will not be rolled back
if the pipeline fails or the DTC otherwise decides the Tx should not be
committed (e.g. if the ASP.NET page was transactional and failed).
-djm
--
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2004 Microsoft Corporation. All rights
reserved.
--------------------
Content-Class: urn:content-classes:message
From: "Ravi Shankar" <shankar.nospam@hp.com>
Sender: "Ravi Shankar" <shankar.nospam@hp.com>
Subject: Pipeline Components & TRANSACTED Pipelines
Date: Thu, 1 Jul 2004 00:04:39 -0700
Lines: 7
Message-ID: <2438e01c45f39$acde2230$a501280a@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Thread-Index: AcRfOazeQTfIKxeCR3SMgkmMa0gsFg==
Newsgroups: microsoft.public.commerceserver.general
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.commerceserver.general:14177
NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
X-Tomcat-NG: microsoft.public.commerceserver.general
Does a pipeline component participating in a transacted
pipeline have to necessarily support transactions ? or
can it have a <Transaction(TransactionOption.NotSupported)
> attribute ?
What would be the issues in such a case ?
[ Post a follow-up to this message ]
| 
