Xrpcc modeler error when trying to generate stub classes from a WSDL

Question

I'm trying to generate JAX-RPC stub classes (both client and server side) from a WSDL in which one of the message parts references a complexType element defined in the <types> section of the WSDL. Here is my little WSDL document:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="Book_Def"
targetNamespace="myTypes"
xmlns:tns="myTypes"
xmlns:xsd1="myTypes"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<xsd:schema targetNameSpace="myTypes"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Book" type="xsd1:BookType"/>
<xsd:complexType name="BookType">
<xsd:all>
<xsd:element name="authors" type="xsd:string" maxOccurs="10"/>
<xsd:element name="preface" type="xsd:string"/>
<xsd:element name="price" type="xsd:float"/>
</xsd:all>
</xsd:complexType>
</xsd:schema>
</types>
<message name="runMyPgm">
<part name="book" type="xsd1:Book"/>
</message>
<message name="getPgmResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="MyPgmIFPortType">
<operation name="runMyPgm">
<input message="tns:runMyPgm"/>
<output message="tns:getPgmResponse"/>
</operation>
</portType>
... Binding stuff
</port>
</service>
</definitions>
I've tried many combinations of defining my complex type and input message and whenever I run xrpcc using this WSDL as input, I get a Error: Modeler error: invalid entity name: Book (in namespace "myTypes"). Sorry if this is a dumb question, but what am I doing wrong in my <types> or <message> definitions to cause this error? I've had some luck generating stubs when the part types are all simple types, but I've not had any luck with getting a <complexType> definition accepted by xrpcc. Thanks in advance for any help you can offer.

Answer 1

Yes you can specify type mapping in configuration file and probably this will solve the problem, but I've never tested this approach. Perhaps I'm not advanced user. Actually the serializerFactory and deserializerFactory are a little vague for me:(