Could be bugs in the name mapping, but note that JAX-RPC has specific rules as to how names in WSDL are mapped to Java names, and Axis tries to follow these rules. At various points in development, this has gotten LOTS of attention. :-)
If a name is mangled, however, the Meta-data (particularly in the JavaBean class) should contain the 'unmangled' XML QName of the member element and this should get used when putting XML on the wire. -- Tom Jordahl Macromedia Server Development -----Original Message----- From: Lasker, Kory [mailto:klasker@;qwest.com] Sent: Tuesday, October 22, 2002 4:07 PM To: '[EMAIL PROTECTED]' Subject: WSDL and SOAP response inconsistencies Can anyone give me a good explanation of why my SOAP-encoded RPC responses do not always obey my mixed case object name and attributes. For example, if I get a simple response back that includes a "StreetAddress" object, why does the SOAP response look like this: ... <multiRef id="id0" SOAP-ENC:root="0" encodingStyle="http://schemas.xmlsoap.org/soap/encoding"; xsi:type="ns4:StreetAddress" xmlns:ns4="http://myuri.org";> <ERRORMSG xsi:type="xsd:string"></ERRORMSG> <REGION xsi:type="xsd:string"></REGION> <streetAddress href="#id1"/> </multiRef> Notice the lower case "s" in streetAddress (this should be StreetAddress according to the WSDL and my objects). Moreover, within the StreetAddress object I have a field called "IsRanged" that is returned by SOAP as "isRanged". Any ideas? Kory
