Namespace is Corrupted in Branching Integration Logic

Under certain circumstances, namespaces can become corrupted in integrations in which you define routing paths for two different target endpoints. For example, this issue may occur if you create an Oracle Sales Cloud connection with the same name that is used for both routing paths, but with different endpoints. Recreating the integration from scratch may not resolve the problem, nor may deleting the connection and also deleting the integration and recreating everything from scratch.

Assume you perform the following steps:

  1. Create a new integration (for example, with the Oracle CPQ adapter as the source connection and Oracle Sales Cloud adapter as the target connection).

  2. Click the Filter icon on the top part of the integration.

  3. Create expression filtering logic in the Expression Builder (for example, oSCQuoteId = "").

  4. Click Show Palette to display the list of available connections and technologies.

  5. Drag a second Oracle Sales Cloud adapter to the target area of the integration and configure it in the adapter configuration wizard by selecting the same services as you did with the initial Oracle Sales Cloud adapter. This second adapter represents the ELSE branch of the routing path.

  6. Click the Filter icon and create different expression filtering logic for the ELSE branch (for example, oSCQuoteId != "").

  7. Save the integration and attempt to create and then modify a quote from Oracle Sales Cloud.

    The quote creation and first save attempt are successful (top part of the branch where oSCQuoteID is null), but the second save fails (on the ELSE branch). The error occurs because the second target is pointing to an older Oracle Sales Cloud instance. The following error is logged, which is due to the namespace being changed on the second branch:

    Invoke JCA outbound service failed with application error, exception:
    com.bea.wli.sb.transports.jca.JCATransportException:
    oracle.tip.adapter.sa.api.JCABindingException:
    oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFExcep
    tion:
    servicebus:/QUOTE_UPSERT_01/Resources/resources/application_106/inbound_616/re
    sourcegroup_516/Update_Sales_Order_REQUEST.wsdl [
    Update_Sales_Order_REQUESTPortType::updateSalesOrderHeader(parameters,paramete
    rs) ] - WSIF JCA Execute of operation 'updateSalesOrderHeader' failed due to:
    oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault
    from server : Unknown method ; nested exception is:
    oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault
    from server : Unknown method
    com.bea.wli.sb.transports.jca.JCATransportException:
    oracle.tip.adapter.sa.api.JCABindingException:
    oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFExcep
    tion:
    servicebus:/QUOTE_UPSERT_01/Resources/resources/application_106/inbound_616/re
    sourcegroup_516/Update_Sales_Order_REQUEST.wsdl [ 
    . . .
    . . .
    . . .