Hi Sanjiva, I would say that Axis2 runninng in the context of a particular server (e.g. Geronimo in this case) is JAX-WS compliant. And, I agree, that is awesome!
Has the JAX-WS TCK been run against Axis2 outside the context of another server? I don't think it has, and I think there is probably additional work to make Axis2 in a standalone environment compliant, for example the deployment code needs to hook in with the MDQ and JAXWS modules. Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: 512-838-4587 or Tie Line 678-4587 Internet e-mail and Sametime ID: [EMAIL PROTECTED] Sanjiva Weerawarana <[EMAIL PROTECTED]> 08/19/2007 12:23 PM Please respond to [email protected] To [email protected] cc Subject Re: status of passing JAX-WS TCK for axis2 R J Scheuerle Jr wrote: > > Correct! > > Release 1.3 of Axis2 successfully commpleted the JAX-WS TCK tests in > Geronimo. > I will update the wiki page. So does this mean that Axis2 is now JAX-WS compliant? If so, AWESOME! Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ --------------------------------------------------------------------- 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]
