"xmlns:xmlns='http://xmlns.oracle.com/bpel/sensor'" Sensor Is Creating Messages With Invalid Namespace Declaration (Doc ID 1372262.1)

Last updated on NOVEMBER 01, 2011

Applies to:

Oracle SOA Platform - Version: 11.1.1.4.0 and later   [Release: 11gR1 and later ]
Information in this document applies to any platform.

Symptoms

When sensor action is created for tracking.ecid property for the composite to send the message to a JMS queue, the resulting XML in the source queue is invalid. When consuming this message from other tools it's throwing the XML is invalid.

Message generated by Sensor Activity:

<actionData xmlns:xmlns='http://xmlns.oracle.com/bpel/sensor' xmlns='http://xmlns.oracle.com/bpel/sensor'>
<header>
<compositeDN>default/HelloWorld!1.0*soa_476612aa-1f84-481e-a1db-e9b98f608075</compositeDN>
<compositeInstanceId>210001</compositeInstanceId>
<componentName>HelloWorld_ep</componentName>
<sensor filter="" sensorName="MySensor" target="undefined" kind="service" xmlns="http://xmlns.oracle.com/bpel/sensor">
<serviceConfig outputNamespace="http://www.w3.org/2001/XMLSchema" outputDataType="string" expression="$in.property.tracking.ecid" operation="execute" service="HelloWorld_ep"/>
</sensor>
</header>
<payload>
<serviceData>d126c29923b443ab:-18a3f374:132735222eb:-7ffd-00000000000005f6</serviceData>
</payload>
</actionData>

In the above payload xmlns:xmlns='http://xmlns.oracle.com/bpel/sensor' is not a valid declaration. Namespace prefix should not be xmlns.

Cause

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 hundreds of Community platforms