How to remove the "Invalid Manifest id generated in ebXml 2.0" message in B2B
Last updated on JANUARY 04, 2017
Applies to:Oracle SOA Platform – B2B (Business to Business) - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11gR1]
Information in this document applies to any platform.
Invalid Manifest Id in ebXML message generated with Oracle B2B 18.104.22.168.0.
In SOA Suite - B2B 11g PS5 (22.214.171.124.0), manifest Id is generated like this:
<eb:Manifest eb:id="0AAB72E3139BF61CD3A000002ECBB8AB" eb:version="2.0">
Notice that the manifest ID starts with a digit: this is not correct as per schema definition
This is confirmed in the schema definition:
Specifically the EBMS 2.0 specification states:
The Manifest element is comprised of the following:
• an id attribute (see section 2.3.7 for details)
• a version attribute (see section 2.3.8 for details)
• one or more Reference elements
2.3.7 id attribute
Each of the ebXML SOAP extension elements defined in this specification has an id attribute which is an XML ID that MAY be added to provide for the ability to uniquely identify the element within the SOAP Message. This MAY be used when applying a digital signature to the ebXML SOAP Message as individual ebXML SOAP extension elements can be targeted for inclusion or exclusion by specifying a URI of "#<idvalue>" in the Reference element.
Additionally the xml:id specification, xml:id is derived from xsd:NCName.
xsd:NCName has the following definition:
"\i" matches any character that may be the first character of an XML name,
Please note that id attribute starts with a digit and not with a letter as per specification.
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