ORABPEL-11017 Error while translating message to native format

Question

Hello I and trying to do a simple read and write file adapter. When I try and map the variables in the xls file it seems to work right but I run the BPEL and I get this output :(
ORABPEL-11017
[2010/01/20 15:52:19]
Faulted while invoking operation "Write" on provider "WriteFileAdaper".
- <messages>
- <input>
- <Invoke_1_Write_InputVariable>
- <part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="readrecord">
- <readrecord xmlns:tns="http://TargetNamespace.com/ReadFileAdapter" xmlns="http://TargetNamespace.com/ReadFileAdapter">
<tns:name/>
<tns:number/>
<tns:email/>
</readrecord>
</part>
</Invoke_1_Write_InputVariable>
</input>
- <fault>
- <bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
- <part name="code">
<code>
null
</code>
</part>
- <part name="summary">
<summary>
file:/C:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_BPELProcess_1.0_f1f4eaf21f2ea0f6ab23787c642f300a.tmp/WriteFileAdaper.wsdl [ Write_ptt::Write(readrecord) ] - WSIF JCA Execute of operation 'Write' failed due to: Translation Error.
Error while translating message to native format [Caused by: Error in definition of native data.
No style found to read the native data for <element name="name">.
Must specify a style at <element name="name"> to read the corresponding native data.
; nested exception is:
     ORABPEL-11017
Translation Error.
Error while translating message to native format [Caused by: Error in definition of native data.
No style found to read the native data for <element name="name">.
Must specify a style at <element name="name"> to read the corresponding native data.
Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
</summary>
</part>
- <part name="detail">
<detail>
null
</detail>
</part>
</bindingFault>
</fault>
</messages>
Here is the XSD:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
targetNamespace="http://TargetNamespace.com/ReadFileAdapter"
xmlns:tns="http://TargetNamespace.com/ReadFileAdapter"
elementFormDefault="qualified"
attributeFormDefault="unqualified" nxsd:encoding="ASCII" nxsd:stream="chars" nxsd:version="NXSD">
<xsd:element name="readrecord">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:string" nxsd:terminatedBy="," nxsd:quotedBy="&quot;">
</xsd:element>
<xsd:element name="number" type="xsd:string" nxsd:terminatedBy="," nxsd:quotedBy="&quot;">
</xsd:element>
<xsd:element name="email" type="xsd:string" nxsd:terminatedBy="${eol}" nxsd:quotedBy="&quot;">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<!--NXSDWIZ:F:\BPEL-Training\insert.txt:-->
<!--USE-HEADER:false:-->

Answer 1

Are you using opaque schema or custom defined schema?
Make your File Outbound Adapter from Opaque to the same Schema as you used for input. Modify the InputVariable to Outbound File Adatper Message Type to the Schema's Element . Modify the PL Property for your Directory Structure for inbound and outbound.