Limitations in the Resequencer

Understanding Message Exchange Patterns of an Oracle Mediator 23-3

23.1.1 The one.way.returns.fault Property

The one.way.returns.fault property controls how faults and one-way messages are handled for one-way interface SOAP calls. You can add this property to the service binding component of the web service section for one-way web services in the composite.xml file. This property is not applicable to references. It is applicable only to services and only to the binding.ws binding type. Table 23–2 provides more details on this property. Table 23–2 one.way.returns.fault Property If one.way.returns.fault Is... Then... Set to true: . . . service name=Mediator1_2 ui:wsdlLocation=ReadFile.wsdl interface.wsdl interface=http:xmlns.oracle.compcbpeladapterfile LocalSandboxProject1ReadFile2Fwsdl.interfaceRead_ ptt binding.ws port=http:xmlns.oracle.compcbpeladapterfile LocalSandboxProject1ReadFile2Fwsdl.endpoint Mediator1Read_pt property name=one.way.returns.fault type=xs:string many=false override=maytrueproperty binding.ws service . . . Any fault that occurs during downstream processing returns a SOAP fault to the client and an HTTP response code of 500. The same behavior as 11g Release 1. Set to false: . . . service name=Mediator1_2 ui:wsdlLocation=ReadFile.wsdl interface.wsdl interface=http:xmlns.oracle.compcbpeladapterfile Local SandboxProject1ReadFile2Fwsdl.interfaceRead_ ptt binding.ws port=http:xmlns.oracle.compcbpeladapterfileLocalSan dboxProject1ReadFile2Fwsdl.endpointMediator1Read_ pt property name=one.way.returns.fault type=xs:string many=false override=mayfalseproperty binding.ws service . . . Any fault that occurs during downstream processing returns only an HTTP response code of 500. No SOAP fault is returned to the client. Not set the default case Any fault that occurs during downstream processing returns a SOAP fault to the client and an HTTP response code of 500. The same behavior as 11g Release 1. 23-4 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite To add the one.way.returns.fault property: 1. In the SOA Composite Editor, select the service binding component to which you want to add the one.way.returns.fault property. 2. Go to the Property Inspector section in the lower right part of the editor.

3. In the Binding Properties section, click the Add icon.

The Create Property dialog is displayed.

4. In the Name field, enter one.way.returns.fault.

5. In the Value field, enter true or false.

6. Click OK.

23.2 Understanding a Request-Reply Message Exchange Pattern

In a request-reply interaction, the Oracle Mediator is invoked and sends a reply to the caller. Depending on the type of routing rule target, the responses, faults, and callbacks are handled as shown in Table 23–3 : Figure 23–2 illustrates the request-reply message exchange pattern. Table 23–3 Response When Oracle Mediator’s WSDL Is a Request Reply Routing Rule Target Type Response Request There is no response from the target, but there should be at least one sequential routing rule with a request-response service. Request Response The response is sent back to the caller. The response can be forwarded to another target or event, but there should be at least one sequential routing rule that returns a response back to the caller. Request Response Fault The response is sent back to the caller. The fault is forwarded to another target or event. Request Callback There is no response from the target, but there should be at least one sequential routing rule with a request-response service. The callback is forwarded to another target or event. Request Response Callback The response is sent back to the caller. The callback is forwarded to another target or event. Request Response Fault Callback The response is sent back to the caller. The callback and fault are forwarded to another target or event. Understanding Message Exchange Patterns of an Oracle Mediator 23-5 Figure 23–2 Request-Reply Message Exchange Pattern

23.3 Understanding a Request-Reply-Fault Message Exchange Pattern

In a request-reply-fault interaction, the Oracle Mediator is invoked and sends a reply and one or more faults back to the caller. Depending on the type of routing rule target, the responses, faults, and callbacks are handled as shown in Table 23–4 : Table 23–4 Response When Oracle Mediator’s WSDL Is a Request Reply Fault Routing Rule Target Type Response Request There should be at least one sequential routing rule with a request-response-fault service. Oracle Mediator returns null when there is no response to be sent. Request Response The response is sent back to the caller. Any exception in Oracle Mediator message processing may result in a fault. Request Response Fault The response and fault are sent back to the caller. Any exception in Oracle Mediator message processing may result in a fault. Request Callback There is no response from the target, but there should be at least one sequential routing rule with a request-response service. Oracle Mediator returns null when there is no response to be sent. The callback is forwarded to another target or event. Request Response Callback The response is sent back to the caller. Any exception in Oracle Mediator message processing may result in a fault. Client One-Way Target Reference or Component Request-Response- Fault Target Reference or Component Request-Response Target Reference or Component Asynchronous Request-Callback Target reference or Component Invoke Null Response Invoke Reply to Client Invoke Callback Fwd Null Response Invoke Response Fault Fwd Request- Response Mediator