Quoting Jack Wang <[EMAIL PROTECTED]>: > > In the normal kandula client side, we will do the ws call as: > > RemoteLoginWs binding = new > RemoteLoginWsServiceLocator().getRemoteLoginWs(); > ((RemoteLoginWsSoapBindingStub)binding).setMaintainSession(true); > result = binding.bizRemoteLogin(userName, password); > > This is not for WS-Security case, if we must use WS-Security, how should we > do? > Does kandula support WS-Security ?
WS-Security is a separate area and I believe there are Apache projects that look into those specifications. The WSAT specification does contain a couple of sections on security but I haven't studied them yet to see whether there's any thing that needs to be handled specifically by Kandula on top of Apache Security implementations. Kandula and Sandesha do not interoperate at present. thanks, --dasarath > > Kandula is great. I use kandula1 with axis1.3 successfully, but I don't know > how about kandula2 > this summer. Should I transfer from kandula1 to kandula2 ? > > Thanks > > Jack Wang > > > > ___________________________________________________________ > ÇÀ×¢ÑÅ»¢Ãâ·ÑÓÊÏä-3.5GÈÝÁ¿£¬20M¸½¼þ£¡ > http://cn.mail.yahoo.com > > --------------------------------------------------------------------- > 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]
