The type of the sequence is actually an array of type: apachesoap:mapItem

I don't think this is the cause of your problem. The WSDL is rpc/encoded
which doesn't really fit the document/literal style that it should be used
with.
I get the typical error message when trying to compile the schema

scomp http://ws.soatrader.com/easycfm.com/1.0/Captcha?WSDL
http://ws.soatrader.com/easycfm.com/1.0/Captcha?WSDL:0: warning: The WSDL http:/
/ws.soatrader.com/easycfm.com/1.0/Captcha?WSDL uses SOAP encoding. SOAP encoding
 is not compatible with literal XML Schema.
http://ws.soatrader.com/easycfm.com/1.0/Captcha?WSDL:40:6: error: src-resolve: t
ype '[EMAIL PROTECTED]://schemas.xmlsoap.org/soap/encoding/' not found.


Is this what you meant by 'cannot compile a sequence'

What errors are you seeing?

As far as fixing the errors above, you will simply need to add the other
xsds to the path when compiling with scomp.
-Jacobd


On 10/22/07, Vance Vagell <[EMAIL PROTECTED]> wrote:
>
> 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]
>
>

Reply via email to