I am happy to say the regression is further up my stack from CXF. I'll
have to sift through the dependencies to see what might be causing this
behavior. The generated client code is identical to my test that now works
with my web service from the command line. My mistaken conclusion that CXF
was to blame, was in assuming one port was being called when it was the
other port with the same name in the WSDL using soap 1.2.
By the way, the ant scripts generated do not allow java versions besides
1.8 and 1.9. My work-around was to add my version (I'm using openJDK 13)
to line 29 of the generated build.xml like:
<condition property="is.supported.java.version">
<or>
<equals arg1="${ant.java.version}" arg2="1.8"/>
<equals arg1="${ant.java.version}" arg2="1.9"/>
<equals arg1="${ant.java.version}" arg2="13"/>
</or>
</condition>
Another change I made to include the jax-ws libraries was to add those
paths to line 94, something similar to:
<pathelement
location="C:\.m2\repository\com\sun\xml\ws\jaxws-tools\2.3.3\jaxws-tools-2.3.3.jar"/>
<pathelement
location="C:\.m2\repository\jakarta\jws\jakarta.jws-api\2.1.0\jakarta.jws-api-2.1.0.jar"/>
On Wed, Apr 14, 2021 at 10:54 AM Freeman Fang <freeman.f...@gmail.com>
wrote:
> 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 <harvestmoon...@gmail.com> 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
> >
>
