Not sure about "disabling" but ... You might want to check out this article by Glen Mazza: http://www.jroller.com/gmazza/entry/soap_client_tutorial If you use the approach of "localizing" the WSDL so that:
1) the WSDL from which you generated your client-side artifacts is packaged into the JAR file with your compiled classes in a specific location visible to the classpath at runtime - avoids the over-the-wire call to instantiate the client proxy 2) you insure your generated client artifacts AND the WSDL used for those are always in sync... the incident of some JAX-WS "mismatch" exception can be avoided should the WSDL at the remote endpoint location ever get changed and you not be aware... (even if a method was added that you're not using, could cause this exception when the proxy does NOT get regenerated). The "address" in the generated code would now be relative to the *classpath *and not a URL over HTTP. Just a suggestion. *HTH* *Mark * On Sun, Nov 17, 2013 at 7:45 AM, Oliver Raupach <[email protected]> wrote: > Hi, > > I have a fairly large wsdl (about 800kb / 700 WebMethods). And I've > noticed that the client reloads the WSDL from the server each time the > client starts.This takes about 4-5 seconds. Can I disable this > "download" to speed up the client statup? > > My client-code looks like this: > > [...] > JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean(); > factory.getInInterceptors().add(new LoggingInInterceptor()); > factory.getOutInterceptors().add(new LoggingOutInterceptor()); > factory.setServiceClass(IClientService.class); > factory.setAddress("http://localhost:8080/webapp/clientService";); > IClientService client = (IClientService) factory.create(); > > DataDto dataDto = client.getData("test"); > [...] > > > -- > > Oliver Raupach > >
