Using predefined WSDL for synchronous client gives error

Question

Generated a new BPEL project and attached our own WSDL (channelInterface.wsdl) to the client partner link. Specified the one and only operation in the receive and reply activities and auto created the variables in each. All simple stuff and the 'validate' reports 0 errors but upon a Project 'make' the following errors are reported.
Rather surprised as this seems to be very simple but the generated code does not seem to auto resolve the types. Any help much appreciated.
Error(19): [Error ORABPEL-10007]: unresolved messageType [Description]: in line 19 of "C:\temp\bpel\Test\BPELProcess1\BPELProcess1.bpel", WSDL messageType "{http://xmlns.oracle.com/BPELProcess1}BPELProcess1RequestMessage" of variable "inputVariable" is not defined in any of the WSDL files. [Potential fix]: Make sure the WSDL messageType "{http://xmlns.oracle.com/BPELProcess1}BPELProcess1RequestMessage" is defined in one of the WSDLs referenced by the deployment descriptor.
The generated .bpel code is:
<process name="BPELProcess1" targetNamespace="http://xmlns.oracle.com/BPELProcess1" xmlns="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:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:ns1="http://channel.abi.ukps.sbs" xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:client="http://xmlns.oracle.com/BPELProcess1" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" 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="ch" partnerLinkType="ns1:ChannelInterface_PL" myRole="ChannelInterface_Role"/>
</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="inputVariable" messageType="client:BPELProcess1RequestMessage"/><!-- Reference to the message that will be sent back to the
requester during callback
-->
<variable name="outputVariable" messageType="client:BPELProcess1ResponseMessage"/>
<variable name="Receive_1_SubmitApplication_InputVariable" messageType="ns1:AbISubmissionRequestMessage"/>
<variable name="Reply_1_SubmitApplication_OutputVariable" messageType="ns1:AbISubmissionResponseMessage"/>
</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 BPELProcess1.wsdl
--><!-- Asynchronous callback to the requester.
Note: the callback location and correlation id is transparently handled
using WS-addressing.
-->
<receive name="Receive_1" partnerLink="ch" portType="ns1:ChannelInterface" operation="SubmitApplication" variable="Receive_1_SubmitApplication_InputVariable" createInstance="yes"/>
<reply name="Reply_1" partnerLink="ch" portType="ns1:ChannelInterface" operation="SubmitApplication" variable="Reply_1_SubmitApplication_OutputVariable"/>
</sequence>
</process>
The deployment descriptor (bpel.xml) is:
<?xml version = '1.0' encoding = 'UTF-8'?>
<BPELSuitcase>
<BPELProcess id="BPELProcess1" src="BPELProcess1.bpel">
<partnerLinkBindings>
<partnerLinkBinding name="ch">
<property name="wsdlLocation">ChannelInterfaceRef.wsdl</property>
</partnerLinkBinding>
</partnerLinkBindings>
</BPELProcess>
</BPELSuitcase>

Answer 1

when you create a new process (and not choose empty type) we create input and output variables for you
<variable name="inputVariable" messageType="client:BPELProcess1RequestMessage"/>
and those still point to the old messagetypes ..
The easiest way is on you left down side in jdev, when the bpel process is opened in the diagram mode you should see the structure (structure pane).. expand variables node and edit those 2 variables, within them right click on the part named payload and choose the new messagetype it is supposed to have
hth clemens