DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16485>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16485 BeanDeserializer error when XML element starts with a capital letter ------- Additional Comments From [EMAIL PROTECTED] 2003-02-17 19:18 ------- Hi ant! The patch you propose makes the BeanDeserializer really "lenient" about the XML it processes, and don't think that's the right solution here. I glanced quickly over the axis-user thread you reference, but I'm not sure I understand the problem. If you're using ".NET generated WSDL" (or any WSDL), the WSDL should define the exact schema expected in the SOAP messages, and Axis' WSDL2Java should generate classes which expect exactly that XML. If the schema says there's an element "<Name>", that will be turned into a field in a JavaBean called "name" (lowercase 'n') to satisfy the normal XML<->Java name mapping rules, but metadata will be inserted into the class to make sure that when serialized/deserialized, we use the uppercase version. We have tests which check this functionality in our regular test suite - so if there's a particular case where you see a failure, could you please attach the WSDL (or a URL to it) and some test code which demonstrates the problem? FYI, if you're talking about a non-Axis-generated bean (i.e. not generated from WSDL2Java) which has been developed to interoperate with some schema- definition, then the developer of that bean is responsible for making sure it has appropriate metadata to match the schema. If I'm misunderstanding the problem, please clarify. Thanks!
