Unparseable XML input: Namespace type defined with different URIs: http://www.myCompany.com/HedgeAccounting and http://www.w3.org/2001/XMLSchema
In my legacy application we send xml message to one of the interfaces.
This XML has in its header this namespace (among few others)
xmlns:type="http://www.myCompany.com/HedgeAccounting I would expect the Namespace to look like this
xmlns:HedgeAccounting="http://www.myCompany.com/HedgeAccounting In a general way: what could be the reason for this difference ?
In your examples, type and HedgeAccounting are both XML namespace prefixes.
XML namespace prefix names themselves are inconsequential. It is only through their binding to an actual XML namespace URI that they derive meaning. Use whatever conventions might apply, or make up your own. You might use ns1, x, or fred, but as with any name, it’s better to have some mnemonic justification. For example, xsd and xs are often used for the XSD namespace.
