Another example is:
http://api.eurocv.eu/euroserver.php?wsdl
The type "License" defined as:
<xsd:complexType name="License">
<xsd:all>
<xsd:element name="license" type="xsd:string"/>
</xsd:all>
</xsd:complexType>
is not loaded. This one has an <all>, instead of a <sequence>, but is the same
behavior.
- Vance
> -------- Original Message --------
> Subject: Single-item sequence causes failure
> From: Vance Vagell <[EMAIL PROTECTED]>
> Date: Mon, October 22, 2007 7:42 pm
> To: [email protected]
>
> Hello,
>
> I'm running into an issue with compiling certain schemas. After much
> testing, I've been able to narrow down the issue. It stems from definitions
> of the following format:
>
> <complexType name="Map">
> <sequence>
> <element maxOccurs="unbounded" minOccurs="0" name="item"
> type="apachesoap:mapItem"/>
> </sequence>
> </complexType>
>
> In particular, it seems that XMLBeans cannot compile a sequence with just one
> element in it. If I add another <element> to this, it works. What's
> interesting is that this does not throw an exception, it fails silently.
> Only when our software (which uses XMLBeans) goes to find the "Map" type does
> it fail, because that type isn't in the list.
>
> Is this a known issue/bug, perhaps with a fix or workaround? Have others
> experienced this problem?
>
> For reference, here is a WSDL file with a <types> section that can be used to
> reproduce this issue (includes example above):
>
> http://ws.soatrader.com/easycfm.com/1.0/Captcha?WSDL
>
> Note that we compile the types programatically at runtime, using
> XmlBeans.compileXsd(). We do not use the provided automated scripts to
> generate Java classes out of the schema.
>
> Thanks,
> Vance
>
>
> ---------------------------------------------------------------------
> 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]
