Open Services Development (OSD) Interface Parser Is Failing for Some Scenarios
Last updated on MARCH 18, 2014
Applies to:Oracle Communications Network Charging and Control - Version 5.0.1 and later
Information in this document applies to any platform.
In Oracle Network Charging and Control version 5.0.1 there is an issue with the Open Services Development (OSD) interface parser. When a SOAP request is sent it's parsed by the interface for HTTP headers. But it is failing because starting point of soap block is being identified with "<soapenv".
This parsing is not working in all scenarios, for example if the name space shortcode as "<env".
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