FitNesse Fixtures - Enabling a FitNesse Fixture to call a method on the Server Side
java,eclipse,web-services,fitnesse,wsimport
There are many ways to do what you describe. You could, for instance, create your own fixture (i.e. class containing test code) in Java that uses the stubs you generated to call your service. Or (what I prefer) is to call the services directly using HTTP posts, configured in the...
Equivalent of org.apache.axis.components.net.SunFakeTrustSocketFactory for wsimport
java,web-services,jax-ws,axis,wsimport
All that's happening in that class is the provision of a bogus trust store manager, that trusts anything. Knowing that, you can use this article and put something together. First the easy trust manager public class EasyTrustManager implements X509TrustManager { public void checkClientTrusted(X509Certificate[] chain, String authType) { //do nothing }...
How to enable WS-A Addressing on my JAX-WS generated client code
You can modify the WSDL as you mentioned, to indicate addressing is required (though I would ask the 3rd party to, if their endpoint truly requires it..). See example 3-1 and 3-2 on the specification for this. You may need to regenerate your client (wsimport); of this I am not...
wsimport result has a different runtime endpoint
java,maven,wsdl,endpoint,wsimport
Yes, I'm answering my own question. I'm doing this for the benefit of anyone of experiences this problem in the future. I've just heard back from the guys hosting the service I've been trying to connect to with the mysteriously changing port. Their server "...is running on our internal network...
does wsimport depend on the original source of the wsdl?
web-services,wsdl,client,jax-ws,wsimport
In principle it works with any wsdl (as long as it follows the standard). Have you tried to download it locally first, in case it wasn't obtained correctly remotely.
“javax.xml.ws.WebServiceException: is not a valid service.” proxy issue?
java,web-services,https,proxy,wsimport
As it turns out, what I was missing was importing the certificate in my local truststore (or better, when I first tried doing so, I thought I was using the correct truststore, but I wasn't). For anyone who may need it, here is an explanation of how to do that...