Exception on CONNECT SOAP related to Namespace null
I have multiple exception like Caused by: java.lang.IllegalArgumentException: Namespace URI may not be null
at com.pega.apache.axiom.om.impl.common.OMNamespaceImpl.<init>(OMNamespaceImpl.java:38) in logs when calling some connect web service.
I don't understand the reason of the namespace null , i checked the WSDL and all namespace are filled.
I tried to simulate through the SOAP UI, but not able to reproduce, even we tried to get the request from some tools susch us Dynatrace and Freesimm in order to check which namespace is empty but no results.
I checked the WSDL for all the ws we used and there is no namespace empty , so how this exception is happened ? and if someone got like this exception before?