BPEL Compilation Error - Take 2 - JoJo

Question

I am looking for is trying to figure out what am I doing wrong for this compile time error message to appear when I try to deploy the BPEL service. The BPEL diagram indicates no errors.
Error:
[Error ORABPEL-10902]: compilation failed
[Description]: in "bpel.xml", XML parsing failed because "undefined WSDL message.
Message "{http://tempuri.org/}AddSoapOut" is not defined in WSDL at "file:/C:/BPELTest/AddInts/bpel/AddInts.wsdl".
Please make sure the spelling of the message name is correct and the WSDL import is complete.
[Potential fix]: n/a.
BPEL Scenario
The scenario is very, very simple.
I have a web service running on my local laptop (front-ended by the IIS app server). It adds two integer numbers and returns the value synchronously, and its WSDL is AdderSvc.wsdl (the same one listed in the error message). The BPEL process is merely kicked off by the "initiate" operation when using the BPEL Control as the client. "Initiate" takes two integer values to be added as inputs, and these two have the message types that map to the same message type that the AdderSvc is using. The BPEL process invokes the AdderSvc, and then invokes the callback to the client (BPEL Control). Very, Very simple stuff.
I am using a local copy of the AdderSvc.wsdl created by cutting and copying from the auto generated WSDL by IIS app server. I did this so that I could manually insert the "partnerLink" definitions into the AdderSvc WSDL as the auto generated WSDL does not describe this. The version of JDeveloper I am using is "Studio Edition Version 10.1.3.1.0.3960".
All my variables, seem in order, but I continue to get the above error message when I try to compile and deploy. Attached are the .bpel and .wsdl files.
Any suggestions will be geratly appreciated
AddInts.bpel file
<process name="AddInts" targetNamespace="http://xmlns.oracle.com/AddInts"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:ns1="http://tempuri.org/"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:client="http://xmlns.oracle.com/AddInts"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<!--
PARTNERLINKS
List of services participating in this BPEL process
-->
<partnerLinks>
<!--
The 'client' role represents the requester of this service. It is
used for callback. The location and correlation information associated
with the client role are automatically set using WS-Addressing.
-->
<partnerLink name="client" partnerLinkType="client:AddInts"
myRole="AddIntsProvider" partnerRole="AddIntsRequester"/>
<partnerLink name="AdderSvc" partnerRole="AddProvider"
partnerLinkType="ns1:Add"/>
</partnerLinks>
<!--
VARIABLES
List of messages and XML documents used within this BPEL process
-->
<variables>
<!-- -->
<!-- Reference to the message passed as input during initiation -->
<variable name="Invoke_1_Add_InputVariable"
messageType="ns1:AddSoapIn"/>
<variable name="Invoke_1_Add_OutputVariable"
messageType="ns1:AddSoapOut"/>
</variables>
<!--
ORCHESTRATION LOGIC
Set of activities coordinating the flow of messages across the
services integrated within this business process
-->
<sequence name="main">
<!-- Receive input from requestor. (Note: This maps to operation defined in AddInts.wsdl) -->
<receive name="receiveInput" partnerLink="client"
portType="client:AddInts" operation="initiate"
variable="Invoke_1_Add_InputVariable" createInstance="yes"/>
<!--
Asynchronous callback to the requester. (Note: the callback location and correlation id is transparently handled using WS-addressing.)
-->
<invoke name="Invoke_1" partnerLink="AdderSvc" portType="ns1:CalcWSSoap"
operation="Add" inputVariable="Invoke_1_Add_InputVariable"
outputVariable="Invoke_1_Add_OutputVariable"/>
<invoke name="callbackClient" partnerLink="client"
portType="client:AddIntsCallback" operation="onResult"
inputVariable="Invoke_1_Add_OutputVariable"/>
</sequence>
</process>
AddInts.wsdl file
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="AddInts"
targetNamespace="http://xmlns.oracle.com/AddInts"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:client="http://xmlns.oracle.com/AddInts"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:nsl="http://tempuri.org/">
     <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     TYPE DEFINITION - List of services participating in this BPEL process
     The default output of the BPEL designer uses strings as input and
     output to the BPEL Process. But you can define or import any XML
     Schema type and use them as part of the message types.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
     <types>
          <schema xmlns="http://www.w3.org/2001/XMLSchema">
               <import namespace="http://xmlns.oracle.com/AddInts" schemaLocation="AddInts.xsd" />
          </schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
               <import namespace="http://tempuri.org/" schemaLocation="AdderSvc.xsd" />
          </schema>
</types>
     <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     MESSAGE TYPE DEFINITION - Definition of the message types used as
     part of the port type defintions
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
     <message name="AddIntsRequestMessage">
          <part name="payload" element="client:AddIntsProcessRequest"/>
     </message>
     <message name="AddIntsResponseMessage">
          <part name="payload" element="client:AddIntsProcessResponse"/>
     </message>
<!--
-->
     <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PORT TYPE DEFINITION - A port type groups a set of operations into
     a logical service unit.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
     <!-- portType implemented by the AddInts BPEL process -->
     <portType name="AddInts">
          <operation name="initiate">
               <!-- <input message="client:AddIntsRequestMessage"/> -->
               <input message="nsl:AddSoapIn"/>
          </operation>
     </portType>
     <!-- portType implemented by the requester of AddInts BPEL process
     for asynchronous callback purposes
     -->
     <portType name="AddIntsCallback">
          <operation name="onResult">
               <!-- <input message="client:AddIntsResponseMessage"/> -->
               <input message="nsl:AddSoapOut"/>
          </operation>
     </portType>
     <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PARTNER LINK TYPE DEFINITION
     the AddInts partnerLinkType binds the provider and
     requester portType into an asynchronous conversation.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
     <plnk:partnerLinkType name="AddInts">
          <plnk:role name="AddIntsProvider">
               <plnk:portType name="client:AddInts"/>
          </plnk:role>
          <plnk:role name="AddIntsRequester">
               <plnk:portType name="client:AddIntsCallback"/>
          </plnk:role>
     </plnk:partnerLinkType>
</definitions>
AdderSvc.wsdl file
<?xml version="1.0" encoding="utf-8" ?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="http://tempuri.org/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
targetNamespace="http://tempuri.org/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/">
<s:element name="Add">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="x" type="s:int" />
<s:element minOccurs="1" maxOccurs="1" name="y" type="s:int" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="AddResult" type="s:int" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
<!--
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://tempuri.org/" schemaLocation="AdderSvc.xsd" />
</schema>
-->
</wsdl:types>
<wsdl:message name="AddSoapIn">
<wsdl:part name="parameters" element="tns:Add"/>
</wsdl:message>
<wsdl:message name="AddSoapOut">
<wsdl:part name="parameters" element="tns:AddResponse"/>
</wsdl:message>
<wsdl:portType name="CalcWSSoap">
<wsdl:operation name="Add">
<wsdl:input message="tns:AddSoapIn"/>
<wsdl:output message="tns:AddSoapOut"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="CalcWSSoap" type="tns:CalcWSSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<wsdl:operation name="Add">
<soap:operation soapAction="http://tempuri.org/Add" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="CalcWS">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/" />
<wsdl:port name="CalcWSSoap" binding="tns:CalcWSSoap">
<soap:address location="http://localhost/CalcWS/CalcWSnew.asmx" />
</wsdl:port>
</wsdl:service>
<plnk:partnerLinkType name="Add">
<plnk:role name="AddProvider">
<plnk:portType name="tns:CalcWSSoap"/>
</plnk:role>
</plnk:partnerLinkType>
</wsdl:definitions>

Answer 1

This problem has been resolved. The primary problem was due to the fact that I was trying to pass variables to the service provider without doing an appropriate assign function. Once the assignment was done the compilation and deployment were successful.
For more information on how to make synchronous BPEL calls to external Web Services, refer to the sample titled 104.SyncQuoteConsumer and read the document in the BPEL help section titled "Invoking Synchronuos Web Service".