Note that <import> (both wsdl and xsd) doesn't change the targetNamespace of the imported namespace (hence the rule about no namespace coercion). <import> just gives you the ability to reference entities from the other namespace.

On 4/20/06, Dies Koper <[EMAIL PROTECTED]> wrote:
Hello Anne, Dink,

> I'm not sure I understand Dies's first recommendation. The targetNamespace
> of the "types" schema should NOT be the same as the imported namespace,
> "ifx". (If you want to incorporate a namespace of the same name, you must
> use <xsd:include> rather than <xsd:import>). You might want to verify the

Sorry, I meant the targetNamespace of the XSD that is being imported.
But I was wrong. I forgot that "Namespace coercion on wsdl:import is
disallowed by the Profile." in the WS-I BP spec (R2005) only applied to
wsdl:import, not to xsd:import.

Regards,
Dies


> On 4/20/06, Dies Koper <[EMAIL PROTECTED] > wrote:
>> Hello Dink,
>>
>> Maybe you can use www.ws-i.org's WS-I test tool to check your WSDL.
>>
>> 1. The target name of your schema (" http://www.ifxforum.org") should be
>> the same as the namespace (now "urn:ifxforum-org") you specify in the
>> xsd:import.
>>
>> 2. The names of the wsdl:input elements ("tns:DoIFXRqMsg" and
>> "tns:DoIFXRsMsg" are not valid NCName values.
>>
>> Other than that it looks okay to me.
>>
>> Regards,
>> Dies
>>
>>
>> Dink wrote:
>>> Hello all,
>>>
>>> I have created a WSDL for a web service called "WS017". The WSDL is
>>> put on http://mis.ccu.edu.tw/~dink/WS017.wsdl . However I can't use
>>> the Axis WSDL2Java tool to produce the stub for this service. Can
>>> somebody help me to check if the WSDL is error? Anyone can use the
>>> command line "java org.apache.axis.wsdl.WSDL2Java
>>> http://mis.ccu.edu.tw/~dink/WS017.wsdl -p stub" to test the WSDL.
>>>
>>> Best Regard, Dink Lo


Reply via email to