The elements are in order. Let me explain the problem a little more clearly. I generated code using a wsdl that does not include the field cdCustType because that field was not in the data. The data now includes that field, but my application does not need it and there is nothing in the generated code about this field. The generated code throws the error when the parser comes to cdCustType.
-----Original Message----- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 10:48 AM To: [email protected] Subject: Re: Axis2 unexpected subelement error Moore, It depends on the schema. *IF* your schema (in your wsdl) says, they are needed only then we throw an exception. We also throw an exception if the schema specifies a certain order and the runtime soap message does not have the same order. -- dims On 11/9/06, Moore, Don H <[EMAIL PROTECTED]> wrote: > > > I have an issue with generated Java code using wsdl2Java and Axis2 > 1.0. I've also tried using Axis2 1.1, Nov 2 2006 build, and have the same problem. > From posts I've found in the archives, I see this has been reported a > few times before, but I haven't found a solution. > > Essentially, if additional fields get added to the data which were not > in the wsdl when the java files were generated with Axis2, then the > code blows up with the java.lang.RuntimeException: Unexpected subelement error. > Obviously, I can regenerate the java code using a new wsdl. But, as > long as those additional fields are not needed in my application, then > I really shouldn't have to be continuously regenerating the java code. > Shouldn't the additional fields just be ignored by the parser? -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
