Rejection Handler Sends Empty Headers When Malformed XML (Doc ID 762724.1)

Last updated on FEBRUARY 03, 2009

Applies to:

Oracle ESB - Version: 10.1.3.1 to 10.1.3.4
This problem can occur on any platform.

Symptoms

You have implemented a WSIF Rejection Handler for a FileAdapter , that points to a BPEL process.

1) When the input XML file is not valid against the XSD (it has a different structure than the one in the XSD but it's a valid XML document), it works fine, and the headers passed through to the error-handling BPEL process are populated with the correct information:

Example :

<tns:RejectedMessage xmlns:tns="http://xmlns.oracle.com/pcbpel/errorHandling"
     tns:RejectionId="INVALID_MSG_null_ReadCustomerData_20081118_102227_0546"
     tns:BatchId="" tns:BatchInfo="" tns:PrimaryKey=""
     tns:MessageOriginReference="">

<tns:MessageHeader>
 <InboundFileHeaderType xmlns="http://xmlns.oracle.com/pcbpel/adapter/file/"> 
  <fileName>LegacyCustomer.xml</fileName>
  <directory>/home/oracle/Customer/In</directory>
  <size>964</size>
  <batch></batch>
  <batchIndex>1</batchIndex>
 </InboundFileHeaderType>
</tns:MessageHeader>

2) When the input XML file is not a valid XML document (e.g. badly-formed XML with
non-matching tags) then the file cannot be parsed and the header data is not passed through to the error-handling BPEL process. The <MessageHeader> is either empty or contains garbage characters:

<tns:MessageHeader><tns:MessageHeader>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms