[Fwd: Re: Kandula 1]

[Dominik Heller]

Dasarath Weeratunge schrieb:

> Quoting Dominik <dominik.heller@...>:
>
>  
>> Dasarath Weeratunge schrieb:
>>    
>>>> Hi Dasarath,
>>>> well first of all thanks so much for all your answers yesterday it
>>>> helped me alot. So I think I am getting closer to understand the
>>>> TxHandler.SO the TxHandler org.apache.kandula.geronimo.TxHandler is used
>>>> to extract the context from the soap message, pass it to a JTA
>>>> Transaction via bridging and bind this tx to the current thread, right?.
>>>> The other TxHandler org.apache.kandula.coordinator.at.TxHandler does
>>>> pretty much the same thing but uses the kandula transaction manager,
>>>> right? So for example if I have a j2ee web service I would use the
>>>> geronimo.TxHandler for incomming calls because of the JTA stuff and I
>>>> would use the other handler to add the context of the tx to the soap
>>>> message, right?
>>>>    
>>>>        
>>> Yes.
>>>
>>> We can also do this the other way as well. What if an EJB want's to call a
>>>      
>>> transactional .NET component?
>>>
>>> -- Dasarath
>>>
>>>
>>>  
>>>      
>>>> So because of the testSuite1, I will work on that in a couple of days
>>>> unfortunately I am busy with my thesis stuff right now and won't have
>>>> the time to work on that for the next two weeks. After that I will be
>>>> more than glad to help.
>>>>
>>>> THX
>>>> -Dominik
>>>>
>>>>    
>>>>        
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: kandula-dev-unsubscribe@...
>>> For additional commands, e-mail: kandula-dev-help@...
>>>
>>>  
>>>      
>> Mmh, my guess is that the EJB would use the TxHandler like the J2EE web
>> service I described and the .NET component would use the TxHandler
>>
>> org.apache.kandula.coordinator.at.TxHandler for incoming and outgoing soap
>> messages, right? So in addition to the other case, when I have a non-J2EE
>> client I also would use the org.apache.kandula.coordinator.at.TxHandler for
>> incoming and outgoing messages, right?
>>    
>
> org.apache.kandula.coordinator.at.TxHandler is not for non-j2ee applications.
> Its for micky mouse applications:-), if you understand what I mean!
>
> A platform like .NET has its own transaction management framework and we will
> need a mechanism similar to org.apache.kandula.geronimo.TxHandler for .NET.
> However let Microsoft takecare of that. So we can safely assume that .NET can
> understand ws-at and spit out ws-at in response and correctly too.
>
> The current implementation of Kandula cannot automatically export existing JTA
> transactions as ws-at contexts. If and when people start using this stuff we
> can consider implementing those features.
>
> -- Dasarath
>
>
>
>
>
>
>
>
>
>
>
>  
>>  
>>
>> thx
>> -Dominik
>>
>>
>>    
>
>
>  

Ah ok so in the case of a .NET service there would be TxHandler similar

to org.apache.kandula.geronimo.TxHandler which uses some kind of
bridging to pass the context to the .NET specific transactionManager.
The reason why the mickey mouse TxHandler is used is to convert the
context to a ws-at specific context and add it to a soap message, right?
thx
-Dominik



---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@...
For additional commands, e-mail: kandula-dev-help@...