Hi Dasarath,
Of course I'm interested in obtaining a copy of the EWS documentation! It
would be useful for my master thesis.
Actually I'm reading the source code of Kandula. I find it very interesting.
There's only one thing that is not very clear to me. I refer to the scenario
of Transaction Inflow. Let's say that an application invokes two different
web service operations hosted by the same remote domain. So two messages
arrive at this domain containing the same context.
On the first invocation, after the context has been imported and a local
branch has been created, the TransactionHandler asks the transaction manager
to associate the new local transaction with the current thread. Right?
On the second invocation a local transaction corresponding to the context is
detected, so there's no need to create a new local transaction. But for the
work of the ws operation invoked to be done in the scope of the same local
transaction already existing, the thread serving this second invocation also
should be associated with the local transaction. Right?
If I didn't make mistakes till now, my question is:
is the underlying Transaction Manager capable of managing multiple threads
working in the scope of the same transaction?
Hope I didn't misunderstand too many things. I'm relatively new to
transactions.
Thanks in advance.
Andrea
----- Original Message -----
From: "Dasarath Weeratunge" <[EMAIL PROTECTED]>
To: "Andrea Di Vincenzo" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Tuesday, November 22, 2005 11:55 PM
Subject: Re: kandula basics
Quoting Andrea Di Vincenzo <[EMAIL PROTECTED]>:
Hi Dasarath,
I have found very useful the documentation at:
http://svn.apache.org/repos/asf/webservices/kandula/branches/Kandula_1/src/html
/ws-tx.htm
I'm sorry, I forgot that this may still be in the svn.
Furthermore, reading it I feel how if it were part of a larger document.
For
example I read:
"...Client Axis Engine calls it's invoke method on request flow [20]... "
What does [20] refers to?
EWS (http://ws.apache.org/ews/) and Kandula were developed together at U
of
Moratuwa, Sri Lanka and above documentation relates to this initial work.
(I
may be able to get a copy of this if you are interested.)
The two projects together provide a JSR 109 implementation that also
handles
propagation of security and transaction contexts along services
invokations
from WS to J2EE and vice-versa.
Do you know why it is not in the architecture guide page of the web site?
Kandula has two parts: a ws-tx implementation and a bridge that handles
transaction propagation between J2EE and WS. Initially we thought of only
having the ws-tx implementation in Kandula and moving the bridging code to
EWS. That's why the second half of the documentation is not in the
architecture guide of Kandula.
thanks,
--dasarath
Best Regards
Andrea
----- Original Message -----
From: "Dasarath Weeratunge" <[EMAIL PROTECTED]>
To: "Andrea Di Vincenzo" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Saturday, November 19, 2005 10:20 PM
Subject: Re: kandula basics
> Quoting Andrea Di Vincenzo <[EMAIL PROTECTED]>:
>
>> Hi all
>>
>> I'm writing my thesis about Web Services and Transactions
>>
>> so I would like to understand the Kandula basics and I'm asking if
>> documentation exists that explains in more detail - than the
>> Architecture
>> Guide does - what happens behind the scene when invoking
>> transaction-aware
>> Web Services in the scope of a JTA Transaction.
>
> Hi Andrea,
>
> Unfortunately we do not have any further documentation on how Kandula
> interfaces with JTA/JTS. The best way to get to know the details would
> be
> to
> download Kandula_1 and run the provided sample. Then you can follow the
> code
> and ask questions on the mailing list.
>
> I may be able to provide you with additional samples that use
> EJBs/JBoss
> that
> demonstrates how transactions are imported/exported to/from J2EE. These
> are not
> available in svn due to copyright issues.
>
> In a nut shell, Kandula uses the JCA 1.5 transaction importing
> mechanism
> to
> import transaction into J2EE.
>
> You may also try the book, (it doesn't talk about importing
> transactions
> but
> talks about ws-tx protocol suite)
> Web Services Platform Architecture : SOAP, WSDL, WS-Policy,
> WS-Addressing,
> WS-
> BPEL, WS-Reliable Messaging, and More (Paperback)
> http://www.amazon.com/gp/product/0131488740/102-4698261-2928158?
> v=glance&n=283155
>
> thanks,
> --dasarath
>
>
>
>>
>> The University of Bologna, Italy, is actually very interested in
>> understanding the internals of Kandula, and I would also like to help
>> some
>> way.
>>
>> Thanks in advance
>> Andrea
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
