Typo. I meant "#3 and #4 will definitely stop a release from happening"...
--- Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Chris, > > Here's what has driven development (this is from my observations) > > #1 Conformance to spec's (SOAP 1.1, 1.2, WSDL 1.1 etc) > #2 Interop using SOAPBuilders forum > #3 Pass the TCK for SAAJ > #4 Pass the TCK for JAXRPC > > #2 will not stop from a release going out, #2 and #3 will definitely stop a release >from > happening. This does not stop folks at various companies from working on WS-I >compatibility and > checking in patches to make it happen (for example soap header support wsdl, >rpc-literal). In > other words, WS-I conformance has never been an issue with releases and though we >have test > suites > for all the SOAPBuilders Interop tests, we don't have one for WS-I conformance. > > Thanks, > dims > > > --- "Peake, Chris" <[EMAIL PROTECTED]> wrote: > > Basic question: > > Does Axis have a goal of being WS-I conformant? > > > > I've read the message traffic tangential to this and I don't see that it is agreed >upon to be > or > > even agreed upon that it should be. > > > > Can someone spell out the current position on this? > > Any thought or detail would be helpful. > > > > thanks, > > chris > > > > > > > > > > > ===== > Davanum Srinivas - http://xml.apache.org/~dims/ > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com ===== Davanum Srinivas - http://xml.apache.org/~dims/ __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
