Anne Thomas Manes wrote to axis-user: >JAX-RPC 1.1 defined standard mappings between Java types and RPC/Encoded, >but it doesn't do the same for Doc/Literal (even though Sun claims it does).
>It could be done as part of JAXB 2.0 or JAX-RPC 2.0, but I'm not convinced >that it belongs in either one. Anyone on this list care to initiate a JSR? Is there any way to gain visibility into the JAX-RPC 2.0 (JSR 224) design discussions? Do I have to become a member of the expert group, or is there anything open to the public? I'd be very curious as to their opinions on this topic. I'm very much of the opinion that there should be one standardized and specified set of W3C XML Schema -> Java mappings THAT ALL JAVA SOAP IMPLEMENTATIONS SHOULD BE MANDATED TO USE. But hell, webMethods GLUE touts its ElectricXML XML -> Java binding engine as one of their discriminating features. WASP likewise touts its robust W3C schema support (substitution groups, etc). So am I dreaming of a utopia that vendors will never agree to? Is it not in a SOAP platform vendor's best interest to make SOAP services implemented on their platform proprietary? Regards, Jonathan Anderson Booz Allen Hamilton
