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: axis-user@ws.apache.org
Subject: Re: A
he.org
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.
-
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: axis-user@ws.apache.org
Subject: Re: Axis2 unexpected subelement error
Moore
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 PROTECTE
Moore,
Check if all the XML elements are in order (according to the schema definition) and also check if all the required elements are there.
I got this error and got rid of it with the above corrections.
Hope this helps,
Sridhar.
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 addi
