Exception building schema because of different namespace

Question

Hi all,
I have a wsdl that define a schema having different namespace from the service itself. When I create an Invoke activity and the input/output variables, everything went ok. However if I try to explore the newly created input/output variables an exception (Problem building schema) is thrown.
If I use the same namespace for the service and the schema defined in it, everything is okay.
Could anybody explain to me why I should set it to the same namespace to get it to work?
Is it a mistake to use different namespace?
Thanks in advance,
santoso
Below is the wsdl :
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="ProposalWSServiceDefinitions4" targetNamespace="http://www.test.com/service" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="http://www.test.com/service" xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://www.test.com/opl" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.test.com/opl">
<complexType name="TProposal">
<sequence>
<element name="id" type="int"/>
<element name="title" type="string"/>
<element name="creator" type="string"/>
<element name="status" type="string"/>
<element name="customerId" type="int"/>
</sequence>
</complexType>
<element name="Proposal" type="tns:TProposal"/>
</schema>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.test.com/service" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="insertProposal">
<xs:complexType>
<xs:sequence>
<xs:element ref="opl:Proposal" xmlns:opl="http://www.test.com/opl"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="insertProposalResponse">
<xs:complexType>
<xs:sequence>
<xs:element ref="opl:Proposal" xmlns:opl="http://www.test.com/opl"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</types>
<message name="insertProposal">
<part element="s0:insertProposal" name="parameters"/>
</message>
<message name="insertProposalResponse">
<part element="s0:insertProposalResponse" name="parameters"/>
</message>
<portType name="ProposalWS">
<operation name="insertProposal" parameterOrder="parameters">
<input message="s0:insertProposal"/>
<output message="s0:insertProposalResponse"/>
</operation>
</portType>
<binding name="ProposalWSServiceSoapBinding" type="s0:ProposalWS">
<s1:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="insertProposal">
<s1:operation soapAction="" style="document"/>
<input>
<s1:body parts="parameters" use="literal"/>
</input>
<output>
<s1:body parts="parameters" use="literal"/>
</output>
</operation>
</binding>
<service name="ProposalWSService">
<port binding="s0:ProposalWSServiceSoapBinding" name="ProposalWSSoapPort">
<s1:address location="http://localhost:7021/Proposal"/>
</port>
</service>
</definitions>

Answer 1

Hi,
The problem is when I use the wsdl in a bpel process project, the variable created can't be explored.
However, I've found the solution by adding import namespace.
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.test.com/service" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://www.test.com/opl" />
<xs:element name="insertProposal">
<xs:complexType>
<xs:sequence>
<xs:element ref="opl:Proposal" xmlns:opl="http://www.test.com/opl"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="insertProposalResponse">
<xs:complexType>
<xs:sequence>
<xs:element ref="opl:Proposal" xmlns:opl="http://www.test.com/opl"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>