wsdl schema import problem

[Ranadhir Nag]

Please indicate if this is not a proper forum for this.
But I get compilation errors when i run wsdlc against this wsdl.
I am using weblogic 10.3,if that is of relevance.

<?xml version="1.0" encoding="UTF-8"?>
<definitions name="PriceListService"
targetNamespace="http://www.ecerami.com/wsdl/PriceListService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.ecerami.com/wsdl/PriceListService.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsd1="http://www.ecerami.com/schema">

<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.ecerami.com/schema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">


<complexType name="ArrayOfString">
<complexContent>
<restriction base="soapenc:Array">
<attribute ref="soapenc:arrayType"
wsdl:arrayType="string[]"/>
</restriction>
</complexContent>
</complexType>
......
......
......

[wsdlc] [WARNING] src-resolve.4.2: Error resolving component 'soapenc:Array'
. It was detected that 'soapenc:Array' is in namespace 'http://schemas.xmlsoap.o
rg/soap/encoding/', but components from this namespace are not referenceable fro
m schema document 'file:/C:/Documents%20and%20Settings/compaq/Local%20Settings/T
emp/_ckr59b/PriceListService.wsdl#types?schema1'. If this is the incorrect names
pace, perhaps the prefix of 'soapenc:Array' needs to be changed. If this is the
correct namespace, then an appropriate 'import' tag should be added to 'file:/C:
/Documents%20and%20Settings/compaq/Local%20Settings/Temp/_ckr59b/PriceListServic
e.wsdl#types?schema1'.


Any ideas on how to resolve this namespace issue will be appreciated.

[Ivan Krizsan]

Hi!
You can resolve the issue and make your service more interoperable by not using the soapenc:Array type and instead using a construct with maxOccurs="unbounded", for instance.
Please refer to the following link for an example: http://www.ws-i.org/Profiles/BasicProfile-1.1.html#soapenc_Array
Best wishes!

[Ranadhir Nag]

Thanks for ther recommendation.
But at a broader level,my concern was why i landed into this namespace issue at the first place.
It seems I am needed to import some namespace - and i may well face this problem for any other namespace too.

Any help in clarify this namespace conflict will be quite helpful

[Ivan Krizsan]

Hi again!
In your case, specifying a schemaLocation for the namespace in question should solve your problem, but be aware that:
In a WSDL document that conforms to the WS-I Basic Profile, importing another WSDL and importing an XML schema containing type declarations are done in two different ways:
Import of WSDL documents must be done using the <wsdl:import> element, while importing an XML schema is to be done using the <xsd:import> element inside a <xsd:schema> element in the <wsdl:types> element.
Examples:

<?xml version="1.0" encoding="UTF-8"?> 
<definitions 
    name="StockQuoteWS" 
    targetNamespace="http://www.somedomain.com/xyz/BookQuote" 
    xmlns:sd="http://www.somedomain.com/xyz/StockQuote" 
    xmlns:soapbind="http://schemas.xmlsoap.org/wsdl/soap/" 
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
    xmlns="http://schemas.xmlsoap.org/wsdl/"> 

    <!-- Import of other WSDL documents is done using the <wsdl:import> element. --> 
    <import namespace="http://www.somedomain.com/xyz/Shipping" 
        location="http://www.somedomain.com/xyz/wsdl/Shipping.wsdl"/>

<types>  
        <!-- 
            This is an example how to import another XML schema into a WSDL 
            document. It must be done inside the <types> element. 
        --> 
        <xsd:schema> 
            <xsd:import namespace="http://www.example.com/SpaceWarGame"  
                schemaLocation="SpaceWarGame.xsd"/> 
        </xsd:schema> 
    </types> 
...

Best wishes!