Hi Oliver On Wed, Jul 21, 2010 at 12:18 PM, Oliver Wulff <[email protected]> wrote:
> Hi Anto > > I know customers which use Web Services for about 9 years. They never had > the requirement for WS-Transaction support because you could sort this out > by the design of the service (WSDL) or they came to the conclusion that > transaction support would have been a nice feature but not really required. > > Instead of calling for instance two operations of a service(s) (transaction > context) you design a less fine grained service which does the work in one > operation you wanted to seperate in two seperate operations. The webservice > is deployed in a application runtime which supports local transactions like > J2EE/EJB. For instance, you define the stateless session bean to create a > new transaction for each incoming request. > > The above approach fits well as long as you don't combine (and tightly > couple) different business components. In such a case, I would have some > objections from an enterprise architecture point of view. > > But what about *business activities* (coordinated with the help of WS-BA or some RESTful approach, does not matter) ? It's a higher level issue compared to the one of creating the right service interface ? cheers, Sergey > Thanks > Oliver > >
