Thanks Dave for the pointer, however, am I the only one to find this quite restrictive? I understand the needs for rules about XML to Java mapping but the first letter uppercase one seems rather cosmetic to me.
I am interested in a solution to this problem. 1 - Should WSDL2Java allow a switch to bypass this uppercase rule? 2 - Should the service's server side code have the provisions to facilitate the mapping? Sylvain. -----Original Message----- From: Dave Dunkin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 06, 2002 5:07 PM To: '[EMAIL PROTECTED]' Subject: RE: [WSDL2Java] No deserializer defined for array type http://[.. .]/: QueryProperty WSDL2Java complies to the JAX-RPC specification for mapping XML identifiers to Java identifiers. That specifies that class should start with a capital letter. Dave -----Original Message----- From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 06, 2002 1:59 PM To: Axis-User (E-mail) Subject: [WSDL2Java] No deserializer defined for array type http://[...]/: QueryProperty Hi all, I am having a problem with caracter case. My complexType is defined as "queryProperty" like : <complexType name="queryProperty"> <sequence> <element name="name" type="types:propertyType" maxOccurs="1"/> <element name="inline" type="xsd:boolean" maxOccurs="1"/> <element name="skipBytes" type="xsd:int" maxOccurs="1"/> <element name="maxBytes" type="xsd:int" maxOccurs="1"/> </sequence> </complexType> but the generated class is "QueryProperty" This seems to be the reason why I get a deserializer exception. Right? This being said, how can the object be serialized in the first place? Question: Although java classes are generaly named starting with an uppercase, shouldn't WSDL2Java respects the capitalization defined in the WSDL? (this is with Axis v22-02-02) -- Sylvain This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.
