Multiple soap modules

Question

hello,
i'm biulding a flex client that works with a soap web servise, i imported the wsdl though the wizard and all was good...
untill i had to use a diffrent module within the same webService.
the other module uses some of the same soap types as the first one(the type's name space is maped to the first module) and vice versa.
as a resoult when i try to import the secound module i get the following error:
The specified ActionScript package already contains a file with the same name
as one of the classes to be generated: <some class name>.as.
Try choosing a different ActionScript package or renaming the existing file.
so naturaly i used a diffrent package, now the problem is that now i have duplicates of the same class in diffrent pakages and one module is overwriting the class deffenitions of the other module in the SchemaTypeRegistry singleton and that is cousing all kinds of weird stuff to happen...
has anyone encounterd this or know how to solve this?
any help would be greatly appreciated.
peleg.

Answer 1

here are examples for the 2 wsdl's:
module 1:
<wsdl:definitions xmlns:tns="http://ns1.something.com/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s2="http://ns2.something.com/" targetNamespace="http://ns1.something.com/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <wsdl:types>
        <s:schema elementFormDefault="qualified" targetNamespace="http://ns1.something.com/">
            <s:import namespace="http://ns2.something.com/" />
            <s:element name="someSOAPElement">
            </s:element>
            <s:element name="someSOAPElementResponse">
                <s:complexType>
                    <s:sequence>
                        <s:element minOccurs="0" maxOccurs="1" name="someSOAPElementResult" type="s2:BillingResponse" />
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:element name="someSOAPType" nillable="true" type="s2:someSOAPType" />
        </s:schema>
        <s:schema elementFormDefault="qualified" targetNamespace="http://ns2.something.com/">
            <s:complexType name="someSOAPType">
            </s:complexType>
        </s:schema>
    </wsdl:types>
    <wsdl:message name="someSOAPElementSoapIn">
        <wsdl:part name="parameters" element="tns:someSOAPElement" />
    </wsdl:message>
    <wsdl:message name="someSOAPElementSoapOut">
        <wsdl:part name="parameters" element="tns:someSOAPElementResponse" />
    </wsdl:message>
</wsdl:definitions>
and module 2:
<wsdl:definitions xmlns:tns="http://ns2.something.com/" xmlns:s="http://www.w3.org/2001/XMLSchema" targetNamespace="http://ns2.something.com/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
  <wsdl:types>
    <s:schema elementFormDefault="qualified" targetNamespace="http://ns2.something.com/">
      <s:complexType name="someSOAPType">
      </s:complexType>
      <s:element name="someSOAPElement">
      </s:element>
      <s:element name="someSOAPElementResponse">
        <s:complexType>
          <s:sequence>
            <s:element name="someSOAPElementResult" type="tns:someSOAPType" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="someSOAPType" nillable="true" type="tns:someSOAPType" />
    </s:schema>
  </wsdl:types>
  <wsdl:message name="someSOAPElementSoapIn">
    <wsdl:part name="parameters" element="tns:someSOAPElement" />
  </wsdl:message>
  <wsdl:message name="someSOAPElementSoapOut">
    <wsdl:part name="parameters" element="tns:someSOAPElementResponse" />
  </wsdl:message>
</wsdl:definitions>
the soap decoder uses mx.rpc.xml.SchemaTypeRegistry, witch is singleton, to map the soap types calss definitions, thus the definitions are shared by all the modules in the application...