Default DAP XPath Search Expression from an Imported WSDL Always Fails
(Doc ID 1985150.1)
Last updated on SEPTEMBER 29, 2023
Applies to:
Oracle Communications Network Charging and Control - Version 5.0.2 and laterOracle Solaris on SPARC (64-bit)
Symptoms
On all version of Oracle Network Charging and Control (NCC), after importing a Web Services Description Language (WSDL) file into Data Access Package (DAP) using the screens, the default XPath search expression provided by DAP does not contain XML namespaces.
The dapIF process however assumes the namespace(s) used by an external Application Service Provider (ASP) is part of the XML tag and will always fail to match the desired element. For example:
Simple Object Access Protocol
A bug introduced in NCC 5.0.2.0 always means the XPath Search Expression cannot be updated in the screens once the DAP operation has been saved. Please see Knowledge Article 1934381.1 for more information on this.
Changes
DAP operations imported from a WSDL file and the default XPath Search Expression left as default.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |