Showing results for 
Search instead for 
Did you mean: 

Incorrect condition evaluation for content-based routing (Receiver determ.)

Former Member
0 Kudos

Hi experts,

We have a SAP XI scenario (using web services), where we use external

definition (an imported WSDL document) of messages, which contain

elements with a default namespace. We have a problem during the

receiver and interface determination, where we use conditions.

When we use an element with a default namespace, it doesn't work (the receiver is not found), e.g. <UserRequest xmlns=

When we add some prefix to the namespace e.g. ns0, it starts working

OK. Problem is, that sender application (web service client) send us

message without a prefix.

What we can do on the side XI? Can you suggest some solution for this problem?

Do you know if SAP XI has some limitation using default namespaces?

In our test system we use SOAP sender adapter and in productive we use external SOAP adapter.

We use SAP XI3.0 (SP19)

Thanks for your help!



Accepted Solutions (1)

Accepted Solutions (1)

Active Contributor
0 Kudos

in your WSDL, edit it and remove the default namespace specified and try the scenario once again. I gather it should work. A trial and error case, but maybe you would find luck.

Answers (1)

Answers (1)

Former Member
0 Kudos

It is OK now. We have already solved the problem. We had to correct a

wsdl and add to it <b>elementFormDefault="qualified"</b> ,

<schema targetNamespace="http://portal.skoda-" xmlns=""


elementFormDefault="qualified" >

The receiver determination started to work correctly. (Our partner apologise for this mistaken wsdl).