Event parameters (elements) sent upstream don't match XSD definition
(Doc ID 1151837.1)
Last updated on DECEMBER 23, 2024
Applies to:
Oracle Communications ASAP - Version 5.2.3 to 5.2.4 [Release 5.2]Information in this document applies to any platform.
Symptoms
There is a mismatch between the ASAPServiceActivation.xsd definition and the ASAP generated events (orderCreateEvent, for instance) elements or parameters that ASAP returns upstream.
For example, the XSD defines serviceState as type sa:serviceStateType, but ASAP returns as type: mslv-sa:ServiceState, which does not exist.
Also for sa:OrderStateType, ASAP returns mslv-sa:OrderState.
Steps To Reproduce:
Send orders through JSRP, subscribe the events.
Go to $ASAP_BASE/samples/jsrp/README for details.
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 |