project with serviced components and non services components

[z f]

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.

 

[Florin Lazar [MSFT]]

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.


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.

 

[z f]

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]]

Non-serviced classes don't change the COM+ context. It will exactly the same
as A calling C. So the answer is yes.

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.

 

[z f]

....and if the same connection object is used in B (non serviced component )
and C (serviced, requires tran)

Non-serviced classes don't change the COM+ context. It will exactly the
same
as A calling C. So the answer is yes.

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.

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.


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.