Below are the details.
Q: Can you explain your scenario/testcase a bit more in detail please?
A: I am testing the webmethods WSDL using SOAP UI. The service intern connects to JBOSS backend.
SOAP UI -> WM flow service -> JBOSS.
Q: Which WebService endpoint do you send the SoapUI-request to?
Q: When sending directly to JBoss, what is the result?
A: We are not getting any error as the data is passed as it is.
Q: Can you try to put a TCP-Monitor in front of the JBoss and send the request (either SoapUI or webMethods) to the TCP-Monitor which will forward it to JBoss.
A: As per present configuration, we could not do it.
Q: Are you using a pregenerated request in SoapUI or is this a custom build request?
SoapUI can create a sample SOAP-Request when the WSDL is imported in which all fields are flled with ‘?’.
A: Yes, I am using request default request created by SOAP UI and replacing the ? with actual values.
As per my analysis, when you specify the nillable attribute to complex type then the actual element in XML will be represent with namespace (xsi:nil=“true” xmlnssi=“http://www.w3.org/2001/XMLSchema-instance” ). Please see attachments.
So, webMethods is adding the namespace even if it is not specified in the request as the nillable property is set to true and it is the way we have to represent the element.
We have removed nillable property for the complex type in WSDL and regenerated the service and sent a request. Now the namespace is not getting added.
Issue occurred because JBOSS was not expecting the namspace in the request where as webMethods is sending it.