I have filed JIRA 3912
https://issues.apache.org/jira/browse/AXIS2-3912
-Jake
Jake Goulding wrote:
Amila:
Thanks for the information. Changing to jaxbri and fixing my code seems
to work now. Is there a high-level overview of what each binding has and
does not have? I'd prefer to not have to find out the hard way that
jaxbri doesn't (for example) support maxOccurs!
I think I will file a JIRA, as the ADB code generation should definitely
throw a warning or error when it sees a mixed type.
-Jake
Amila Suriarachchi wrote:
ADB does not support mixed attribute in complex types.
So either you can
1. change your schema to
<xs:element name="description" type="xs:string">
<!--<xs:complexType mixed="true"/>-->
</xs:element>
2. use different data binding framwork
eg. -d jaxbri -d xmlbeans
thanks,
Amila.
On Tue, Jul 15, 2008 at 2:48 AM, Jake Goulding <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hey all:
I keep getting this error:
org.apache.axis2.AxisFault:
org.apache.axis2.databinding.ADBException: Unexpected subelement node
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
vivisimo.VivisimoVelocityQueryServiceStub.fromOM(VivisimoVelocityQueryServiceStub.java:5494)
at
vivisimo.VivisimoVelocityQueryServiceStub.Simple(VivisimoVelocityQueryServiceStub.java:194)
at Main.main(Main.java:24)
Caused by: java.lang.Exception:
org.apache.axis2.databinding.ADBException: Unexpected subelement node
at
vivisimo.VivisimoVelocityQueryServiceStub$Vce$Factory.parse(VivisimoVelocityQueryServiceStub.java:2092)
at
vivisimo.VivisimoVelocityQueryServiceStub.fromOM(VivisimoVelocityQueryServiceStub.java:5488)
... 2 more
Caused by: org.apache.axis2.databinding.ADBException: Unexpected
subelement node
at
vivisimo.VivisimoVelocityQueryServiceStub$Vce$Factory.parse(VivisimoVelocityQueryServiceStub.java:2086)
However, I took the schema from my WSDL and the XML returned over
the wire, ran them through the W3 XML Validator [1], and it passed.
I added some extra prints to the generated code, and can see the
following code path:
parsing a Vce
parsing a VceChoice
parsing a Tree_type0
parsing a Node_type0
parsing a NodeChoice
parsing a Node_type0
parsing a NodeChoice
parsing a Description
Which seems that it gets to vce/tree/node/node[1], but doesn't
correctly see that vce/tree/node/node[2] should be in the array.
I have attached the WSDL, the SOAP response, a small test program,
and a Wireshark dump of the traffic.
Any advice would be highly appreciated!
-Jake
[1] http://www.w3.org/2001/03/webdata/xsv
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
--
Amila Suriarachchi,
WSO2 Inc.
---------------------------------------------------------------------
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]
