In http://ws.apache.org/kandula/, it said: " Presently, the implementation 
only supports atomic
transaction coordination type. Business activities will be supported in 
future.", so calling two
methods distributed at two machine, as illustrated following, is not supported 
yet, isn's it ? And
when will it be supported ? This summer ? I am eager to use this function. I 
think is is more
important then the interoperability with other implementations of 
WS-Coordination,
WS-AtomicTransaction and WS-BusinessActivity. As for new application we can 
implement the web
service with the same architecture.


--- Jack Wang <[EMAIL PROTECTED]>写道:
> --- Dasarath Weeratunge <[EMAIL PROTECTED]>写道:
> > > 
> > > the last question: to try interopibm, i have to use
> > > this kandula.properties? ->
> > > 
> > > # ending '/' required
> > > 
> > > kandula.context=http://wsi.alphaworks.ibm.com:8082/
> > 
> > Nope. kandula.context should be set the the URL under which axis services 
> > are 
> > deployed. Most often this is http://localhost:8080/axis/services. However, 
> > to 
> > try the interop IBM sample and interop with IBM you need to expose your 
> > Kandula 
> > interop service. Unless you have access to a public server where you could 
> > deploy kandula, try forwarding a port on such a server to your local 
> > machine. 
> > (HTTP tunneling) For instance when I test this, I forward the port 44444 on 
> > lore.cs.purdue.edu to 8081 of my machine. Note that you don't need to do 
> > this 
> > if you test Kandula client side against Kandula InteropService since both 
> > are 
> > on your machine.
> 
> 
>   I don't get it yet. Let's say an example. Machina A has a web service(ws) 
> wsA with method
> updateAMoney() and machine B also has a ws wsB with method updateBMoney(). 
> Let's suppose the url
> are: http://machinaA:8080/axis/wsA and http://machinaB:8080/axis/wsB.
> 
>   Now in a third machine named localHost, I should deploy kandula to call 
> wsA'a updateAMoney()
> and
> wsB's updateBMoney() in one transaction. Localhost could have or not have 
> axis service. When
> localhost has no axis deploied, it maybe a standalone application, and when 
> it has axis
> deploied,
> it maybe a web application. In both case, according to "kandula.context 
> should be set the the
> URL
> under which axis services are deployed.", I guess kandula can not do a 
> transaction to call two
> ws
> methods in different machine.
> 
>   If kandula can call two ws methods in different machine, for example  wsA'a 
> updateAMoney() and
> 
> wsB'a updateBMoney(),let's check example InitiatorApp.
>   
>   InteropServiceSoapBindingImpl.java has many methods, but in mine
> MyServiceSoapBindingImpl.java,
> there is only one method getString(). If I want to do database transaction in
> MyServiceSoapBindingImpl.java, should I add method updateAMoney() in 
> MyServiceSoapBindingImpl?
> Should I add codes like in InteropServiceSoapBindingImpl?
>     TransactionManagerImpl tm = TransactionManagerImpl.getInstance();
>     commit(java.lang.String part)...
>     rollback(java.lang.String part)...
> 
>   How to use the parameter part ? What's the function of inner class 
> XA_OKParticipant? Should I
> write all the code like InteropServiceSoapBindingImpl in mine 
> MyServiceSoapBindingImpl.java? How
> can I add database transaction operation in MyServiceSoapBindingImpl? 
> 
>   Thanks.
> 
> 
> 
> 
> 
> Wang Jun
> 
> 
>       
> 

Wang Jun


Wang Jun


        

        
                
___________________________________________________________ 
雅虎1G免费邮箱百分百防垃圾信 
http://cn.mail.yahoo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to