Hi Dominik,
> if I want to use a client to invoke a web service running on a web
server using
>atomic transactions, is it necessary for my Client ro run on a
webserver too?
This is a tricky question.
In general, only web services may participate as a resource in a WS-*
transaction.
You refer to the "client", which I understand as the business logic
driving the transaction. This role is normally called initiator.
Usually, you do need a web server -- in fact, a web service container
with a deployed transaction software, eg Kandula -- even to run your
initiator.
If you take a look at the WSAT port types Kandula uses, you'll notice
that the commitOperation or rollbackOperation methods are void, so you
do not get the actual outcome of the transaction back.
So how is this done? Upon termination of the transaction, the
Coordinator invokes the Coordinator Completion participant's protocol
services's committedOperation or abortedOperation operation to indicate
the actual result. So, for WS-AT, yes, you'll need a fully-fledged
Kandula instance living in a web service container to support your
client application.
There is one thing I noticed: you mentioned a command-line client, and a
web service that is being called. Where in your scenario does the WS-AT
Coordinator run?
Best regards and good night ;-)
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
