Hi, Thanks for reporting this issue, and yes, a reproducer definitely is more helpful here.
Freeman On Wed, Apr 14, 2021 at 2:42 PM Brian K <[email protected]> wrote: > Hi, > > I think I have discovered an error where the SOAP client is not sending a > parameter consistent with the WSDL. > > I'm not sure exactly when this behavior started. I've been using a > generated client from version 2 and have had good results. For all the 3.x > versions I've tried, it seems that the client is sending the parameter > without its namespace. e.g. > > <ns1:method1 xmlns:ns1="ak.oo"> > <param1>The missing param value</param1> > </ns1:method> > > where it should have: > <ns1:method1 xmlns:ns1="ak.oo"> > <ns1:param1>The missing param value</ns1:param1> > </ns1:method> > > I observed this from tracing with Wireshark, and confirmed this by > downloading the 3.4.3 distribution and running: > > wsdl2java -all myWSDL.wsdl > > Running ant for the client and server, I see that the client's parameter is > not being recognized by the server. I used soapUI to call the server and > the parameter was recognized. > > Can you confirm this scenario and make a test case for it? Would it help > for me to create a sample WSDL to demonstrate? > > Thanks! > Brian >
