Glad it worked for you.
In the upcoming release, the tool will provide a WARNING message about
the unsupported versions of XMLSchema.
Regards,
-Arun
Richard Monson-Haefel wrote:
>Thanks! That did it. I'm amazed at how many typos the WSDL 1.1 Specification
>has. The XMLSchema namespace aside, there are numerous errors in every
>example, which makes those examples invalid. Anyway, using the 2001
>namespace for XMLSchema did that trick (along with fixing a lot of other
>errors).
>
>Richard
>--
>Richard Monson-Haefel
>Author of J2EE Web Services (Addison-Wesley 2003)
>Author of Enterprise JavaBeans, 3rd Edition (O'Reilly 2001)
>Co-Author of Java Message Service (O'Reilly 2000)
>http://www.jMiddleware.com
>
>Arun Gupta wrote:
>
>>Hi Richard,
>>
>>The schema version supported by the xrpcc tool is
>>http://www.w3.org/2001/XMLSchema. And that's why you are getting this
>>error message.
>>
>>Thanks for your interest in JAX-RPC.
>>
>>Regards,
>>-Arun
>>
>>Richard Monson-Haefel wrote:
>>
>>>Hi,
>>>
>>>I think there may be a bug in the xrpcc tool. I've attempted to several
>>>different WSDL to Java code generations with xrpcc and it just doesn't
>>>seem to work. I keep getting the same error.
>>>
>>>"error: modeler error: invalid entity name: "string" (in namespace:
>>>"http://www.w3.org/2000/10/XMLSchema")"
>>>
>>>I an attempt to elliminate my own typos and other bugs I used examples
>>>WSDL files from the WSDL 1.1 specification (http://www.w3.org/TR/wsdl),
>>>but they gave exactly the same errors*. I used examples 1, 4, and 5.
>>>
>>>I have attached my WSDL files and xrpcc config files in the hope that
>>>someone can either help fix the problem. The WSDL files are taken from
>>>the WSDL 1.1 Specification so they should work.* The error consistently
>>>states that my entity name "string" is wrong. I've tried a lot of
>>>different WSDL files to fix the problem but I just doesn't work for me.
>>>I've tried changing the use of type to element as an attribute for the
>>>part element but this doesn't work.
>>>
>>>It seems that I can only use an XSD type if its assigned to a type
>>>attribute of a <part/> and if the style of the soap:binding is "rpc" and
>>>if the soap:input and soap:output use SOAP 1.1 encoding. Other
>>>combinations, such as using types defined in the types element or using
>>>XSD types with document style bindings and literal encoding just doesn't
>>>work.
>>>
>>>Thanks,
>>>
>>>Richard * I had to make a couple fixes to these WSDL 1.1 examples,
>>>because they all had an extra '>' at the end of an operation element and
>>>also example 5 failed to declare a QName for wsdl prefix
>>>
>>>
>>>--
>>>Richard Monson-Haefel
>>>Author of J2EE Web Services (Addison-Wesley 2003)
>>>Author of Enterprise JavaBeans, 3rd Edition (O'Reilly 2001)
>>>Co-Author of Java Message Service (O'Reilly 2000)
>>>http://www.jMiddleware.com
>>>
>>--
>>=============================================
>>There is only one me, I must live myself!
>>There is only one today, I must live itself!
>>=============================================
>>http://members.tripod.com/~apgupta/index.html
>>=============================================
>>
--
=============================================
There is only one me, I must live myself!
There is only one today, I must live itself!
=============================================
http://members.tripod.com/~apgupta/index.html
=============================================