Is there a way to use local xsd elements in WSDL - xsd

Question

I can't seem to use local xsd element in the WSDL schema, since i can't create an external xsd (project conditions).
<types>
<xsd:schema xmlns:fs_req="urn:rg:fs_req" xmlns:sf_facto="urn:rg:sf_facto">
<xsd:import namespace="urn:rg:sf_facto" schemaLocation="ROOT_sf_facto_SF_facto_V00_05.xsd" />
<xsd:import namespace="urn:rg:fs_req" schemaLocation="ROOT_fs_req_fs_req_V00_04.xsd" />
<xsd:element name="getDetailsAction1" type="fs_req:fs_req_fs_req" /
<xsd:element name="getDetailsAction1Response" type="sf_facto:SF_facto_SF_facto"/>
</xsd:schema>
</types>
Below the call of the xsd element (Not valide part!)
<message name="detailMpaResponse">
<part name="getDetail" element="tns:getDetailsAction1Response" />
</message>
<message name="detailMpaRequest">
<part name="getDetailResponse" element="tns:getDetailsAction1" />
</message>
How can i have a valide wsdl with the local xsd element?

Answer 1

The problem looks to be with your namespace qualifier in the <part> nodes.
EDIT:
In looking closer at your original post I think the schema element might hold the values we need. Give this code a shot:
<message name="detailMpaResponse">
<part name="getDetail" element="fs_req:getDetailsAction1Response" />
</message>
<message name="detailMpaRequest">
<part name="getDetailResponse" element="sf_facto:getDetailsAction1" />
</message>

Answer 2

You need to declare a new targetNamespace for the xs:schema in your wsdl:types and add it to wsdl:definitions, something like this:
<types>
<xsd:schema xmlns:types="urn:rg:types" targetNameSpace="urn:rg:types" xmlns:fs_req="urn:rg:fs_req" xmlns:sf_facto="urn:rg:sf_facto">
<xsd:import namespace="urn:rg:sf_facto" schemaLocation="ROOT_sf_facto_SF_facto_V00_05.xsd" />
<xsd:import namespace="urn:rg:fs_req" schemaLocation="ROOT_fs_req_fs_req_V00_04.xsd" />
<xsd:element name="getDetailsAction1" type="fs_req:fs_req_fs_req" />
<xsd:element name="getDetailsAction1Response" type="sf_facto:SF_facto_SF_facto"/>
</xsd:schema>
</types>
then add the new namespace to wsdl:definitions:
xmlns:types="urn:rg:types"
and then refer to it in the message parts:
<message name="detailMpaResponse">
<part name="getDetail" element="types:getDetailsAction1Response" />
</message>
<message name="detailMpaRequest">
<part name="getDetailResponse" element="types:getDetailsAction1" />
</message>
The new namespace can't match the ones you import.

Answer 3

Just did a quick experiment (using Eclipse WSDL editor), and the following code was generated when I selected "using a type" from an external XSD (in the same directory as the WSDL file):
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.example.org/NewWSDLFile/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="NewWSDLFile"
targetNamespace="http://www.example.org/NewWSDLFile/" xmlns:xsd1="http://www.example.org/NewXMLSchema">
<wsdl:types>
(...)
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.example.org/NewXMLSchema"
schemaLocation="NewXMLSchema.xsd">
</xsd:import>
</xsd:schema>
</wsdl:types>
<wsdl:message name="NewOperationRequest">
<wsdl:part name="parameters" type="xsd1:externalSchemaParamType" />
</wsdl:message>
(...)
In your case: is "tns" the name space of the externa XSD?