Rejected Message Handlers in OSB

Question

The official documentation of Oracle JCA adapters
http://docs.oracle.com/cd/E12839_01/integration.1111/e10231/life_cycle.htm#BABBHJEA
says that one can have a Web Service invoked whenever the JCA File Adapter rejects a message,
and this invokation would include the error details.
However, I have found examples only for a BPEL Error Handler, and not a WebService Error Handler.
I have tried providing a dynamic JCA activation property "rejectedMessageHandlers=wsif:// http:// pierrepc:7001/ errorhandler/ rejectionMessagePS? WSDL | handleRejection | message" , where myhandler is the URL of a Proxy Service based on a WSDL, but I keep getting the error
"Error while trying to hand off bad message to Rejection handler wsif : // http: // pierrepc:7001/ errorhandler / rejectionMessagePS?WSDL | handleRejection | message due to: Unable to find an available port"
The WSDL is:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<definitions name="RejectionMessage"
targetNamespace="http://xmlns.oracle.com/pcbpel/rejectionHandler"
xmlns:tns="http://xmlns.oracle.com/pcbpel/rejectionHandler"
xmlns:err="http://xmlns.oracle.com/pcbpel/errorHandling"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>
<!-- Message Type for JCA Adapter Framework onReject() callback -->
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/pcbpel/errorHandling"
schemaLocation="JCAErrorHandling.xsd"/>
</schema>
</types>
<message name="RejectionMessage">
<part name="message" element="err:RejectedMessage"/>
</message>
<portType name="RejectionHandlerPortType">
<operation name="handleRejection">
<input message="tns:RejectionMessage"/>
</operation>
</portType>
<binding name="rejectedmessageSOAP" type="tns:RejectionHandlerPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="handleRejection">
<soap:operation soapAction="http://www.example.org/rejectedmessage/handleRejection"/>
<input>
<soap:body use="literal"/>
</input>
</operation>
</binding>
<service name="rejectedmessage">
<port binding="tns:rejectedmessageSOAP" name="rejectedmessageSOAP">
<soap:address location="http://www.example.org/"/>
</port>
</service>
</definitions>
and the XSD is
<?xml version="1.0" encoding="UTF-8"?>
<schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/pcbpel/errorHandling" xmlns:tns="http://xmlns.oracle.com/pcbpel/errorHandling" xmlns="http://www.w3.org/2001/XMLSchema">
<element name="FatalErrorMessage" type="tns:FatalErrorMessageType"/>
<complexType name="FatalErrorMessageType">
<sequence>
<element name="Originator" type="string"/>
<element name="Reason" type="string"/>
<element name="Exception" type="string"/>
<element name="StackTrace" type="string"/>
</sequence>
</complexType>
<element name="RejectedMessage" type="tns:RejectedMessageType"/>
<complexType name="RejectedMessageType">
<sequence>
<element name="MessageHeader" type="base64Binary"/>
<element name="MessagePayload" type="base64Binary"/>
<element name="RejectionReason" type="string"/>
<element name="AdditionalProperties" type="tns:AdditionalPropsType"/>
</sequence>
<attribute name="RejectionId" type="string"/>
<attribute name="BatchId" type="string"/>
<attribute name="BatchInfo" type="string"/>
<attribute name="PrimaryKey" type="string"/>
<attribute name="MessageOriginReference" type="string"/>
</complexType>
<complexType name="AdditionalPropsType">
<sequence>
<element name="RejectionProp" type="tns:RejectionPropType" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="RejectionPropType">
<simpleContent>
<extension base="string">
<attribute name="name" type="ID" use="required"/>
<attribute name="value" type="string" use="required"/>
</extension>
</simpleContent>
</complexType>
</schema>
Any clue?
I have invoked successfully the Proxy Service with the original WSIF libraries from Apache http://ws.apache.org/wsif/wsif_samples/index.html .... I don't see why the collaxa-third party library in the Oracle Adapter refuse to parse the WSDL...
thanks!
Edited by: Pierluigi Vernetto on 27-Jan-2012 04:22

Answer 1

Maybe this can help - http://www.javamonamour.org/2011/11/osb-and-rejectedmessagehandlers-in-jca.html