-
1. Re: wsconsume not picking up -w ?
zhurlik Nov 13, 2019 10:04 AM (in response to nickarls)Hi,
Could you try to use the option -wsdlLocation
-wsdlLocation wsdlLocation
Specifies the value of the @WebServiceClient annotation's wsdlLocation property.
Thanks,
Vlad
-
2. Re: wsconsume not picking up -w ?
nickarls Nov 13, 2019 10:14 AM (in response to zhurlik)Tried, same result. I can of course edit the source file manually and re-build a jar but just though I might be missing something simple
-
3. Re: wsconsume not picking up -w ?
zhurlik Nov 14, 2019 1:26 AM (in response to nickarls)hmm... could you try add prefix "/" in the wsdlLocation
-
4. Re: wsconsume not picking up -w ?
nickarls Nov 14, 2019 1:31 AM (in response to zhurlik)already tried / and öaskdfölkasdfölk, it's not just reacting to the parameter
-
5. Re: wsconsume not picking up -w ?
nickarls Nov 15, 2019 12:31 AM (in response to nickarls)I’m also a bit confused regarding what the WSDL document is needed for after client generation. I generated clients for three sevices. Two of them don’t even care if I rename the included file I’m referring to in the WAR. And even that one is satisified with just the WSDL-file and not the XSDs it imports
-
6. Re: wsconsume not picking up -w ?
zhurlik Nov 15, 2019 1:01 AM (in response to nickarls)is it possible to extract your example to be able to play with that locally?
-
7. Re: wsconsume not picking up -w ?
nickarls Nov 15, 2019 1:44 AM (in response to zhurlik)In this case it's a bit tricky since the WSDL is only distributed on request by the government ;-) Which is a bit strange since the service is written to specifications that are public and the WSDL doesn't have any service definitions that would reveal servers (which are behind mutual TLS anyway). But the wsdlLocation should be reproducible with any document, I think