Namespace Prefix In Request From SOAPUI Causing SAXParseException
(Doc ID 2238853.1)
Last updated on MARCH 29, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.13.0 and laterInformation in this document applies to any platform.
Symptoms
On : 7.5.0.13.0 version, Webservices Mgr & JCA Adaptor
Namespace Prefix in Request from SOAPUI causing SAXParseException
The requirement is that the BRM in-bound web services either
a) use namespace prefix in both request/response or
b) not use them in both request/response
Currently, it is inconsistent in a way that request XML does not expect namespace prefix.
However, BRM web service package is 'hard coding' namespace prefix in the response regardless.
SOAPUI is giving following error when adding namespace prefix to all the elements in the request
Request
<bus:XXX_OP_SUBSCRIPTION_QUOTE_PRICE_Request>
0
<bus:XXX_OP_SUBSCRIPTION_QUOTE_PRICE_inputFlist>
0.0.0.1 /account -1
RDMBAN
<bus:ACCOUNT_NO>0.0.0.1 /account 12345
<bus:GL_SEGMENT>
01360
Response
soapenv:Server
org.xml.sax.SAXParseException; Root tag empty,XXX_OP_SUBSCRIPTION_QUOTE_PRICE_in
ERROR
-----------------------
Changes
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 |