hello dan,

i provided a simple service & test case for this issue in bugzilla.
hope it's usefull..

by the way:
the exception does not happen if you use rpc style.

andreas
----- Original Message ----- 
From: "Dan Kamins" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 08, 2003 10:46 AM
Subject: Re: confusion: are embedded complex types possible with axis or
not?



There is a fairly complicated issue regarding complex types (nested, in
arrays, etc.) and some of the code that handles them (including WSDL2Java
autogenerated code) which has changed from Axis v1.0 to v1.1 and broken some
applications (mine included, with that same exception).  Forcing xsi-types
to be specified may help in some cases.

Follow the conversation on the bug [1], and if you have any data points or
test cases to contribute, PLEASE do so, as it's not clear yet how to address
this problem and all of its various permutations.  There is also another [2]
thread about this.

[1] Bugzilla bug report:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21389

[2] Another thread regarding this issue:
http://marc.theaimsgroup.com/?l=axis-user&m=105762712913743&w=2

--
Dan Kamins

On Tue, 8 Jul 2003 10:27:48 +0200, Andreas Bohnert wrote:
>Hi,
>
>there are some posting to that topic but there seems to be no
>conclusion.
>
>there is an example from Rhett.DeWall
>http://marc.theaimsgroup.com/?l=axis-user&m=105657899026622&w=2
>
>if you have something like this:
>
><EmployeeVO>
><firstName>John</firstName>
><lastName>Doe</lastName>
><phone>
><area>999</area>
><location>9999</location>
><prefix>999</prefix>
></phone>
></EmployeeVO>
>
>you will end in the following client error:
>org.xml.sax.SAXException: Invalid
>element in com.sybase.test.util.EmployeeVO - area at
>org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeseri
>alizer.
>java:252)
>
>so SAX is looking inside Employeee and not inside Phone!
>
>i run into the same problem with a similar example. i'm using
>document
>styles.
>is there a solution?
>thanks!
>
>andreas
>
>


Reply via email to