My Oracle Support Banner

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

Last updated on FEBRUARY 03, 2009

Applies to:

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


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=""
     tns:BatchId="" tns:BatchInfo="" tns:PrimaryKey=""

 <InboundFileHeaderType xmlns=""> 

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:



To view full details, 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 a vibrant support community of peers and Oracle experts.