I realize that Axis doesn't currently conform to WS-I Basic Profile, but I would think that there'd be some consensus that it would be a "good thing" to consider making it happen. Given that IBM, Macromedia, and Borland all participate in WS-I, and they all use Axis within their products, I'd expect that they'll push to make it happen.
WS-I is the only formal organization that is attemption to ensure interoperability for the current round of Web services specs (SOAP 1.1, WSDL 1.1, UDDI 2.0). Only UDDI 2.0 will ever achieve the status of an official standard (via OASIS). W3C isn't doing anything around these specs. W3C is developing SOAP 1.2 and WSDL 1.2. SOAP 1.2 might be finished by Q1 next year. WSDL 1.2 won't be finished until Q4 next year (if they maintain their current schedule). So if interoperability is an important goal within the next 12-18 months, WS-I Basic Profile is the only way to go. (And by the way, W3C is not an official international de jure standards organization. It's just a consortium of vendors that work together to develop specifications using a process governed by the bylaws of the consortium. WS-I is also a consortium of vendors that work together to develop specifications using a process governed by the bylaws of the consortium. I don't really see much difference. I've participated in standards development at W3C, OASIS, UDDI, and WS-I. Each consortium has slightly different bylaws, but for the most part, the process is the same.) Anne > -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 20, 2002 2:34 PM > To: [EMAIL PROTECTED] > Subject: Re: UTF-16 with Axis > > > > > > > Anne wrote: > > > R1012 MESSAGEs MAY be serialized as either UTF-8 or UTF-16. > > > > > > In order to be conformant to the WS-I Basic Profile, a SOAP > service (and > > the > > > SOAP implementation it uses) must support both UTF-8 and UTF-16. From > the > > > profile: > > Anne, > > Who says Axis conforms to the WS-I profile? Its's not like they are some > widely recognised standards body like the w3c. Axis (and JAX-RPC) uses > stuff that the basic profile doesnt like, specifically rpc/encoded soap by > default. > > Regarding encoding, SOAP is XML, compliant XML parsers all handle UTF-16 > encoding. So specification wise, it aint an issue. > > There is an implementation issue, to wit: what does Axis send > down the wire? > That is left as experiment to the reader -and remember, you have > the source > to fix things if they dont work. >
