Eb prefix mandatory for inbound ebMS?

Question

Hi,
I am testing Oracle B2B 11g with an ebMS client that does not use the prefix eb for the ebMS namespace.
This clients uses
xmlns:ns4="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"
instead of
xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"
I believe this is a problem for Oracle B2B when resolving the party type.
In the log I see EBMSExchangePlugin: processParty: party type is null, setting it as ebmsIdentifier.
In the wire message we have <ns4:PartyId ns4:type="urn:osb:oin">12345678</ns4:PartyId>In the same way it is a problem to extract the service from<ns4:Service ns4:type="urn:osb:services">afleverservice</ns4:Service>which results in "B2B-51928: Message header validation failed. The received Service Type does not match with the configured {1}"
Is this a bug? Am I missing something?
Groeten,
HJH

Answer 1

OK Anuj.
Here is the packed message that is processed succesfully.
After changing eb to another prefix I get B2B-51928
Message header validation failed. The received Service Type does not match with the configured {1}
After reverting this change the message is processed succesfully again.
Groeten,
HJH
------=_Part_34_11367412.1302157461593
Content-Type: text/xml; charset=UTF-8
Content-Id: <soappart>
<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"><SOAP-ENV:Header xsi:schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:MessageHeader xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" SOAP-ENV:mustUnderstand="1" eb:version="2.0"><eb:From><eb:PartyId eb:type="ebMS Identifier">33445566</eb:PartyId></eb:From><eb:To><eb:PartyId eb:type="ebMS Identifier">12345678</eb:PartyId></eb:To><eb:CPAId>CPA_Afleverservice</eb:CPAId><eb:ConversationId>12424</eb:ConversationId><eb:Service eb:type="urn:osb:services">afleverservice</eb:Service><eb:Action>afleveren</eb:Action><eb:MessageData><eb:MessageId>[email protected]</eb:MessageId><eb:Timestamp>2011-04-07T08:24:21.515+02:00</eb:Timestamp></eb:MessageData><eb:DuplicateElimination/></eb:MessageHeader><eb:AckRequested xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" SOAP-ENV:actor="urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH" SOAP-ENV:mustUnderstand="1" eb:signed="false" eb:version="2.0"/></SOAP-ENV:Header><SOAP-ENV:Body xsi:schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:Manifest xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" eb:version="2.0"><eb:Reference eb:id="Payload-0" xlink:href="cid:Payload-0" xlink:type="simple"/></eb:Manifest></SOAP-ENV:Body></SOAP-ENV:Envelope>
------=_Part_34_11367412.1302157461593
Content-Type: text/xml; charset=us-ascii
Content-ID: <Payload-0>
<hallo><hallo>over?</hallo></hallo>
------=_Part_34_11367412.1302157461593--