Strange BEPLC compile error

Question

Hello,
I am getting the following error when I attempt to compile a newly created BPEL process using version 10.0.1.2.:
[bpelc] file:/C:/Java/cmsynergy/mmiller/ekc/Esmee~mmiller/Esmee/esmee-process/ESMEE_OrderStatus/ESMEE_OrderStatus.ws
dl
[bpelc] file:/C:/Java/cmsynergy/mmiller/ekc/Esmee~mmiller/Esmee/esmee-process/ESMEE_OrderStatus/OrderDB.wsdl
[bpelc] file:/C:/Java/cmsynergy/mmiller/ekc/Esmee~mmiller/Esmee/esmee-process/ESMEE_OrderStatus/Orderstatus_table.xs
d
[bpelc] [Error] ESMEE_OrderStatus.wsdl:6:79: s4s-elt-schema-ns: The namespace of element 'definitions' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
[bpelc] [Error] ESMEE_OrderStatus.wsdl:6:79: s4s-elt-invalid: Element 'definitions' is not a valid element in a sche
ma document.
[bpelc] [Error] ESMEE_OrderStatus.wsdl:6:79: src-include.1: The root element of document 'file:/C:/Java/cmsynergy/mm
iller/ekc/Esmee%7Emmiller/Esmee/esmee-process/ESMEE_OrderStatus/ESMEE_OrderStatus.wsdl' has to have the namespace name '
http://www.w3.org/2001/XMLSchema' and the local name 'schema'.
[bpelc] [Error] OrderDB.wsdl:10:46: s4s-elt-schema-ns: The namespace of element 'definitions' must be from the schem
a namespace, 'http://www.w3.org/2001/XMLSchema'.
[bpelc] [Error] OrderDB.wsdl:10:46: s4s-elt-invalid: Element 'definitions' is not a valid element in a schema docume
nt.
[bpelc] [Error] OrderDB.wsdl:10:46: src-include.1: The root element of document 'file:/C:/Java/cmsynergy/mmiller/ekc
/Esmee%7Emmiller/Esmee/esmee-process/ESMEE_OrderStatus/OrderDB.wsdl' has to have the namespace name 'http://www.w3.org/2
001/XMLSchema' and the local name 'schema'.
[bpelc] BPEL validation failed.
[bpelc] BPEL source validation failed, the errors are:
[bpelc]
[bpelc] [Error ORABPEL-10902]: compilation failed
[bpelc] [Description]: in "bpel.xml", XML parsing failed because "undefined part element.
[bpelc] In WSDL at "file:/C:/Java/cmsynergy/mmiller/ekc/Esmee~mmiller/Esmee/esmee-process/ESMEE_OrderStatus/ESMEE_Or
derStatus.wsdl", message part element "{http://esmee.ekc.nl/model}ESMEE_OrderStatusProcessResponse" is not defined in an
y of the schemas.
[bpelc] Please make sure the spelling of the element QName is correct and the WSDL import is complete.
The error started appearing in one of my other projects for no apparent reason. I created a new project and started adding things to it and recompiling until the same error started to appear. The change that seems to cause the problem is the addition of a database adapter partnerlink. This caused the adtiion of the 'OrderDB.wsdl' and the error started to appear.
My previous project had been compiling, deploying and running and I did NOT change anything in the project. So I presume the error is caused by some change in my environment, but I can't think what it might be.
If I validate the wsdl files using JDeveloper, the ESMEE_OrderStatus.wsdl reports NO errors, but the OrderDB.wsdl reports:
Validating C:\Java\cmsynergy\mmiller\ekc\Esmee~mmiller\Esmee\esmee-process\ESMEE_OrderStatus\OrderDB.wsdl
Schema element not found: QName(http://xmlns.oracle.com/pcbpel/adapter/db/top/ESMEEOrderStatus, OrderDBSelect_idInputParameters)
Validate WSDL: has errors.
Here is the contents of the Order.wsdl (all generated by JDeveloper):
<?xml version="1.0" encoding="UTF-8"?>
<definitions
name="OrderDB"
targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/db/OrderDB/"
xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/db/OrderDB/"
xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"
xmlns:pc="http://xmlns.oracle.com/pcbpel/"
xmlns:top="http://xmlns.oracle.com/pcbpel/adapter/db/top/ESMEEOrderStatus"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/top/ESMEEOrderStatus"
schemaLocation="Orderstatus_table.xsd"/>
</schema>
</types>
<message name="OrderstatusCollection_msg">
<part name="OrderstatusCollection" element="top:OrderstatusCollection"/>
</message>
<message name="OrderDBSelect_id_inparameters">
<part name="OrderDBSelect_id_inparameters" element="top:OrderDBSelect_idInputParameters"/>
</message>
<message name="Orderstatus_msg">
<part name="Orderstatus" element="top:Orderstatus"/>
</message>
<portType name="OrderDB_ptt">
<operation name="merge">
<input message="tns:OrderstatusCollection_msg"/>
</operation>
<operation name="insert">
<input message="tns:OrderstatusCollection_msg"/>
</operation>
<operation name="update">
<input message="tns:OrderstatusCollection_msg"/>
</operation>
<operation name="write">
<input message="tns:OrderstatusCollection_msg"/>
</operation>
<operation name="delete">
<input message="tns:OrderstatusCollection_msg"/>
</operation>
<operation name="OrderDBSelect_id">
<input message="tns:OrderDBSelect_id_inparameters"/>
<output message="tns:OrderstatusCollection_msg"/>
</operation>
<operation name="queryByExample">
<input message="tns:Orderstatus_msg"/>
<output message="tns:OrderstatusCollection_msg"/>
</operation>
</portType>
<binding name="OrderDB_binding" type="tns:OrderDB_ptt">
<jca:binding />
<operation name="merge">
<jca:operation
InteractionSpec="oracle.tip.adapter.db.DBWriteInteractionSpec"
DescriptorName="ESMEEOrderStatus.Orderstatus"
DmlType="merge"
MappingsMetaDataURL="toplink_mappings.xml" />
<input/>
</operation>
<operation name="insert">
<jca:operation
InteractionSpec="oracle.tip.adapter.db.DBWriteInteractionSpec"
DescriptorName="ESMEEOrderStatus.Orderstatus"
DmlType="insert"
MappingsMetaDataURL="toplink_mappings.xml" />
<input/>
</operation>
<operation name="update">
<jca:operation
InteractionSpec="oracle.tip.adapter.db.DBWriteInteractionSpec"
DescriptorName="ESMEEOrderStatus.Orderstatus"
DmlType="update"
MappingsMetaDataURL="toplink_mappings.xml" />
<input/>
</operation>
<operation name="write">
<jca:operation
InteractionSpec="oracle.tip.adapter.db.DBWriteInteractionSpec"
DescriptorName="ESMEEOrderStatus.Orderstatus"
DmlType="write"
MappingsMetaDataURL="toplink_mappings.xml" />
<input/>
</operation>
<operation name="delete">
<jca:operation
InteractionSpec="oracle.tip.adapter.db.DBWriteInteractionSpec"
DescriptorName="ESMEEOrderStatus.Orderstatus"
DmlType="delete"
MappingsMetaDataURL="toplink_mappings.xml" />
<input/>
</operation>
<operation name="OrderDBSelect_id">
<jca:operation
InteractionSpec="oracle.tip.adapter.db.DBReadInteractionSpec"
DescriptorName="ESMEEOrderStatus.Orderstatus"
QueryName="OrderDBSelect"
MappingsMetaDataURL="toplink_mappings.xml" />
<input/>
</operation>
<operation name="queryByExample">
<jca:operation
InteractionSpec="oracle.tip.adapter.db.DBReadInteractionSpec"
DescriptorName="ESMEEOrderStatus.Orderstatus"
IsQueryByExample="true"
MappingsMetaDataURL="toplink_mappings.xml" />
<input/>
</operation>
</binding>
<!-- Your runtime connection is declared in
J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml
These 'mcf' properties here are from your design time connection and
save you from having to edit that file and restart the application server
if ESMEEDataSource is missing.
These 'mcf' properties are safe to remove.
-->
<service name="OrderDB">
<port name="OrderDB_pt" binding="tns:OrderDB_binding">
<jca:address location="ESMEEDataSource"
UIConnectionName="ESMEEDataSource"
ManagedConnectionFactory="oracle.tip.adapter.db.DBManagedConnectionFactory"
mcf.DriverClassName="oracle.jdbc.driver.OracleDriver"
mcf.PlatformClassName="oracle.toplink.oraclespecific.Oracle9Platform"
mcf.ConnectionString="jdbc:oracle:thin:@ossdbd1:2832:cuross"
mcf.UserName="esmee"
mcf.Password="7D46CB284877A72CC1E112510894EA90DE2D591D9362080D"
/>
</port>
</service>
<plt:partnerLinkType name="OrderDB_plt" >
<plt:role name="OrderDB_role" >
<plt:portType name="tns:OrderDB_ptt" />
</plt:role>
</plt:partnerLinkType>
</definitions>
I've been staring at this for two days and I still got no clue:(

Answer 1

As you mentoined:
"I am getting the following error when I attempt to compile a newly created BPEL process using version 10.0.1.2."
Is it possible to close all windows in JDev, stop and start JDeveloper and create a new process? A create a new partner-link to access the database adapater?
BTW: if you created a PL for the DBadapater, it is not possible to re-enter the DB wizard. It will mess up the toplink/bpel configuration