z
Thu Oct 06 08:14:18 CDT 2005
...and if the same connection object is used in B (non serviced component )
and C (serviced, requires tran)
"Florin Lazar [MSFT]" <florinlazar@online.microsoft.com> wrote in message
news:OtdO01SyFHA.596@TK2MSFTNGP12.phx.gbl...
> Non-serviced classes don't change the COM+ context. It will exactly the
> same
> as A calling C. So the answer is yes.
>
> "z f" <dont@send.mails> wrote in message
> news:OAOAg7xxFHA.3556@TK2MSFTNGP12.phx.gbl...
> shouldn't be problems with transaction scope
> when a services component (A) that is required a transaction
> calls a non serviced (B) component that calls a services component (C)
> that
> is marked as supports,
> in this case will the third (C) component run inside the transaction
> created
> by the first component (A)?
>
> thanks.
>
> "Florin Lazar [MSFT]" <florinlazar@online.microsoft.com> wrote in message
> news:Okgn4pxxFHA.1132@TK2MSFTNGP10.phx.gbl...
>> No and no.
>>
>> Regards--
>> Florin Lazar - Microsoft - [
http://blogs.msdn.com/florinlazar ]
>> <Enjoy transactional programming with System.Transactions!>
>> Please do not send email directly to this alias. This alias is for
>> newsgroup
>> purposes only.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "z f" <dont@send.mails> wrote in message
>> news:eHiIYVNxFHA.3740@tk2msftngp13.phx.gbl...
>> i have a project and i want few of my components to be services.
>> but other classes i don't declare as serviced.
>> should this cause any problem?
>> and what if a seviced object calls a non services object (that might call
>> another serviced component), can this cause problems?
>>
>> TIA for any info on the subject.
>>
>>
>>
>
>
>