> In fact, Georg and I are currently working on an Kandula_1 > implementation of WS-BA since Axis2 and hence Kandula2 didn't seem > reasonably stable at the time of our decision. > We got activiation and registration up and running and are currently > working on the protocol implementation and custom extensions.
this great news:) I'd say at this point, just get it working on either Kandula1 or Kandula2. once we have the things figured out, we can then worry about the particular axis flavour. In fact I'm trying to port the current Kandula1 code to Axis2 these days so that we have a single/stable Kandula code base across both axis versions. if you are generating stubs for WS-BA using wsdl/xsd please send in the wsdl/xsd so that we can add it in as a test case for axis2. at the moment axis2 1.0 does not generate code for kandula1 wsdl/xsd. Presently, Kandula2 uses the OM directly to generate messages but I'm not too happy with this approach. thanks, --dasarath > Having said that, it seems to me that a port to Kandula_2 won't be a big > challenge: the protocol specific parts are seperated from the web > service/axis specific parts, so all we'd need are some extensions of the > kandula2 services and it's done. > > > > -hannes > > --------------------------------------------------------------------- > 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]
