Namespace Empty Errors
Last updated on SEPTEMBER 19, 2017
Applies to:Oracle Communications Order and Service Management - Version 7.2.4 and later
Information in this document applies to any platform.
The goal of this KM article is to overview the OSM 7.2.4/7.3.5 behavioral changes with regards to XML handling. This behavior is more correct in terms of XML semantics but it is not consistent with the previous behaviors in OSM 7.2.2.x. Cartridges that worked previously in OSM 7.2.2.x no longer work correctly in OSM 7.2.4.x or OSM 7.3.5.
For XML DataType content in the default namespace, OSM 7.2.2 implicitly replaces the default namespace (xmlns="") with the enclosing document's default namespace.
In 7.2.4, the content retains its default namespace. This is a backward incompatibility that can cause XPath expressions to select different or no content in 7.2.4.x compared to 7.2.2.x.
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