wsimport forgets one proxy class

I use wsimport to generate the proxy classes from the WSDL file. Class A gets generated, but the class B which corresponds to the A's parameter for its constructor - not. What could be the reason for that? Thx.

Here is the WSDL:

<?xml version='1.0' encoding='UTF-8'?><!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.4-b01-. --><!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.4-b01-. --><definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://project-project.org/ref" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://project-project.org/ref" name="MyName">
<types>
<xsd:schema>
<xsd:import namespace="http://purl.org/dc/terms/" schemaLocation="http://X.X.X.X:8080/myName/MyName?xsd=1" />
</xsd:schema>
<xsd:schema>
<xsd:import namespace="http://project-project.org/ref/tools" schemaLocation="http://X.X.X.X:8080/myName/MyName?xsd=2" />
</xsd:schema>
<xsd:schema>
<xsd:import namespace="http://project-project.org/ref/datatypes" schemaLocation="http://X.X.X.X:8080/myName/MyName?xsd=3" />
</xsd:schema>
<xsd:schema>
<xs开发者_如何学Pythond:import namespace="http://project-project.org/ref/ProjectService" schemaLocation="http://X.X.X.X:8080/myName/MyName?xsd=4" />
</xsd:schema>
<xsd:schema>
<xsd:import namespace="http://project-project.org/ref/MyName" schemaLocation="http://X.X.X.X:8080/myName/MyName?xsd=5" />
</xsd:schema>
<xsd:schema>
<xsd:import namespace="http://project-project.org/ref" schemaLocation="http://X.X.X.X:8080/myName/MyName?xsd=6" />
</xsd:schema>
<xsd:schema>
<xsd:import namespace="http://project-project.org/objects" schemaLocation="http://X.X.X.X:8080/myName/MyName?xsd=7" />
</xsd:schema>
</types>
<message name="MyName">
<part name="parameters" element="tns:MyName" />
</message>
<message name="MyNameResponse">
<part name="parameters" element="tns:MyNameResponse" />
</message>
<message name="ProjectServicePull">
<part name="parameters" element="tns:ProjectServicePull" />
</message>
<message name="ProjectServicePullResponse">
<part name="parameters" element="tns:ProjectServicePullResponse" />
</message>
<portType name="MyName">
<operation name="MyName">
<input message="tns:MyName" />
<output message="tns:MyNameResponse" />
</operation>
<operation name="ProjectServicePull">
<input message="tns:ProjectServicePull" />
<output message="tns:ProjectServicePullResponse" />
</operation>
</portType>
<binding name="MyNamePortBinding" type="tns:MyName">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<operation name="MyName">
<soap:operation soapAction="http://project-project.org/ref/MyName" />
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
</operation>
<operation name="ProjectServicePull">
<soap:operation soapAction="http://project-project.org/ref/ProjectService/Pull" />
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
</operation>
</binding>
<service name="MyName">
<port name="MyNamePort" binding="tns:MyNamePortBinding">
<soap:address location="http://X.X.X.X:8080/myName/MyName" />
</port>
</service>

It could be that your schemas are incomplete for class B and therefore jaxb cannot successfully create the class. if i understand you correctly, you are saying that the generated class A will not compile after generation due to missing classes? does wsimport spit out any warnings?