My Oracle Support Banner

APPS Adapter is Modifying the Incoming Message Namespace Incorrectly (Doc ID 456812.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Enterprise Service Bus - Version 10.1.3.3 and later
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

On ESB 10.1.3.3.0

Find that the Apps Adapter is modifying the incoming message namespace to add an extra suffix which is not necessary.

$ORACLE_HOME/opmn/logs/opmn.log:

07/08/13 22:14:54 Inside my apps adapter onMessage
07/08/13 22:14:54 This is case of business event outbound
07/08/13 22:14:54 nparihar:getAppsEventSchema!!!
07/08/13 22:14:54 retrieved event data : <document xmlns="http://customer.<br>com/customerRS">
<customer>
....
07/08/13 22:14:54 printed event_data parsed payload
07/08/13 22:14:54 Namespace of this record is http://xmlns.oracle.com/xdb/APPS/recvBECust
07/08/13 22:14:54 modified ns = http://xmlns.oracle.com/xdb/APPS/recvBECust/recvBECust
07/08/13 22:14:54 Done processing
07/08/13 22:14:54 Created a new domsource and set documentPayload to it


As you can see from the following statement from opmn.log:

07/08/13 22:14:54 modified ns = http://xmlns.oracle.com/xdb/APPS/recvBECust/recvBECust

The adapter code is modifying the incoming message namespace to add extra suffix (recvBECust) which is not necessary.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.