PawPatrol
Member
JD Edwards EnterpriseOne, Application Release E920 , Tools Release 9.2.5.1
I have created a custom BSSV object using JAX-WS to consume a SOAP API. I created a proxy using the WSDL link provided to me. The proxy folder has a "....porttype.java" file that contains information about request wrapper, response wrapper and their namespaces, also the parameter namespaces.
I test this proxy by assigning parameter values to java variables and passing the variables into a call to xxxport.concernedMethod(inpurvar1, inputvar2, and so on)
I get a fault string exception from the server due to the missing namespace prefix for the request parameters. The reason is faulty XML payload generated by my BSSV class.
I see the XML payload in the log, it has namespace prefix missing for the request parameters(image attached).
If I manually add the missing "ns0" prefix for my XML payload and re-run the request via SoapUI, it works correctly.
Any ideas as to why my BSSV class is adding the namespace prefix correctly to the request wrapper tags ( <ns0 : paymentInstrumentRequest....> and </<ns0 : paymentInstrumentRequest> ), but not adding it to the request parameter tags?
Is the BSSV class code missing something? or is the WSDL XSD faulty?
I have created a custom BSSV object using JAX-WS to consume a SOAP API. I created a proxy using the WSDL link provided to me. The proxy folder has a "....porttype.java" file that contains information about request wrapper, response wrapper and their namespaces, also the parameter namespaces.
I test this proxy by assigning parameter values to java variables and passing the variables into a call to xxxport.concernedMethod(inpurvar1, inputvar2, and so on)
I get a fault string exception from the server due to the missing namespace prefix for the request parameters. The reason is faulty XML payload generated by my BSSV class.
I see the XML payload in the log, it has namespace prefix missing for the request parameters(image attached).
If I manually add the missing "ns0" prefix for my XML payload and re-run the request via SoapUI, it works correctly.
Any ideas as to why my BSSV class is adding the namespace prefix correctly to the request wrapper tags ( <ns0 : paymentInstrumentRequest....> and </<ns0 : paymentInstrumentRequest> ), but not adding it to the request parameter tags?
Is the BSSV class code missing something? or is the WSDL XSD faulty?