L
Lars Siden
Hi,
I'm doing a study on how to implement Transactionmanagement into our coming
..Net projects. We have earlier worked with Sybase XA and BEA Tuxedo so this
is our first Enterprise project where we will use transactions and other
enterprise services in .Net.
Our plan so far is to make a thin URL-loaded winform client that uses
Webservices as underlying applicationlayer. Having studied some of resources
on MSDN about enterprise development I'm still quite puzzled ;-)
The links that I've read can be seen here:
http://www.sidens.se/lazzeslinks.htm
My idea of architecture is like this:
1. Webservice object instantiate
( TransactionOption.Required )
2. A Com+ TransactionManagerObject that instantiates
( TransactionOption.Supported )
3. One or more dbWorker objects
My Questions:
1. Should this work? Is it a good pattern? Should I be better of not using
nr 1 the webservice and instead use a COM+ v1.5 object as Webservice?
2. Examples, are there any complete examples to study?
3. Do I have to register my classes ( C# .NET ) that inherits from
ServicedComponent?
Patterns:
What I would like to achieve is the following:
A Webservice makes a method call.
This method call involves several transactionalobjects
If one or more of the transactionalobjects fail,
rollback everything
else Commit
All ideas, example code and further reading recommendations are very
welcomed!
Best regards,
Lars Siden
Datarutin AB
Stockholm, Sweden
I'm doing a study on how to implement Transactionmanagement into our coming
..Net projects. We have earlier worked with Sybase XA and BEA Tuxedo so this
is our first Enterprise project where we will use transactions and other
enterprise services in .Net.
Our plan so far is to make a thin URL-loaded winform client that uses
Webservices as underlying applicationlayer. Having studied some of resources
on MSDN about enterprise development I'm still quite puzzled ;-)
The links that I've read can be seen here:
http://www.sidens.se/lazzeslinks.htm
My idea of architecture is like this:
1. Webservice object instantiate
( TransactionOption.Required )
2. A Com+ TransactionManagerObject that instantiates
( TransactionOption.Supported )
3. One or more dbWorker objects
My Questions:
1. Should this work? Is it a good pattern? Should I be better of not using
nr 1 the webservice and instead use a COM+ v1.5 object as Webservice?
2. Examples, are there any complete examples to study?
3. Do I have to register my classes ( C# .NET ) that inherits from
ServicedComponent?
Patterns:
What I would like to achieve is the following:
A Webservice makes a method call.
This method call involves several transactionalobjects
If one or more of the transactionalobjects fail,
rollback everything
else Commit
All ideas, example code and further reading recommendations are very
welcomed!
Best regards,
Lars Siden
Datarutin AB
Stockholm, Sweden