Ryan,
My comments inlined...
Ryan LeCompte wrote:
> Vivek,
>
> Thanks for responding. Unfortunately this WSDL was not written by me
> so I don't have much control over it. I believe it is rpc/encoded,
> however, since some of the operations are defined as:
>
>
> <soap:binding style="rpc"
> transport="http://schemas.xmlsoap.org/soap/http"/><operation
> name="XXX"><soap:operation soapAction="urn:XXX"
> style="rpc"/><input><soap:body use="encoded" namespace="urn:XXX"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>
> Does this mean that I can't get wsimport to generate code from this
> WSDL? wscompile was able to generate code for this, however it did
> display various warnings (but didn't stop the source generation
> process). I've noticed at the top of the WSDL that it defines
> namespaces like this:
>
Ok, so it is RPC/ENC wsdl. Well, wsimport does not support rpc/encoding
so it wont be able to consume this wsdl as rpc/enc is not supported.
wscompile is a different tool it comes from JAXRPC RI and it supported
RPC/ENC.
-vivek.
> <definitions xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/
>
> xmlns:xsd=http://www.w3.org/2001/XMLSchema
>
> xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
>
> xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/
>
> xmlns:tns="urn:XXX"
>
> xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/
>
> xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/
>
> xmlns=http://schemas.xmlsoap.org/wsdl/
>
> targetNamespace="urn:XXX">
>
> <types><xsd:schema targetNamespace="urn:XXX">
>
> <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
>
> <xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
>
> ...
>
>
> Ryan
>
> ------------------------------------------------------------------------
> *From:* Vivek Pandey [mailto:Vivek.Pandey_at_Sun.COM]
> *Sent:* Wed 1/17/2007 3:02 PM
> *To:* users_at_jax-ws.dev.java.net
> *Subject:* Re: wsimport doesn't support rcp style wsdl?
>
> Yes it does support rpc/literal style but not rpc/encoded. From the
> stack trace it looks like you have SOAP-ENC:Array thats a soap encoded
> data type.
>
> So check your wsdl if you have included the schema that defines this type.
>
> -vivek.
>
> Ryan LeCompte wrote:
> > Does wsimport work with rcp/literal WSDL files?
> >
> > I'm getting errors from a WSDL that used to work with wscompile on
> > JWSDP 1.6. The errors are similar to the following:
> >
> > [WARNING] src-resolve: Cannot resolve the name 'SOAP-ENC:Array' to
> > a(n) 'type definition' component.
> > line 9 of file:/C:/jaxws-ri/jaxws-ri/bin/Example.wsdl#types?schema1
> > [ERROR] undefined simple or complex type 'SOAP-ENC:Array'
> > line 9 of file:/C:/jaxws-ri/jaxws-ri/bin/Example.wsdl
> > [ERROR] undefined attribute 'SOAP-ENC:arrayType'
> > line 10 of file:/C:/jaxws-ri/jaxws-ri/bin/Example.wsdl
> > [ERROR] undefined simple or complex type 'SOAP-ENC:Array'
> > line 29 of file:/C:/jaxws-ri/jaxws-ri/bin/Example.wsdl
> > [ERROR] undefined attribute 'SOAP-ENC:arrayType'
> > line 30 of file:/C:/jaxws-ri/jaxws-ri/bin/Example.wsdl
> > [ERROR] undefined simple or complex type 'SOAP-ENC:Array'
> > line 42 of file:/C:/jaxws-ri/jaxws-ri/bin/Example.wsdl
> > [ERROR] undefined attribute 'SOAP-ENC:arrayType'
> > line 43 of file:/C:/jaxws-ri/jaxws-ri/bin/Example.wsdl
> >
> > Any ideas?
> >
> > Thanks,
> > Ryan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
>