|
Replies:
1
-
Last Post:
Jul 14, 2009 10:06 AM
by: coding
|
|
|
|
|
|
|
Metro initialization performance
Posted:
Jul 12, 2009 10:26 PM
|
|
|
I could have sworn I saw something on one of the Metro pages about Metro no longer needing to download the WSDL at runtime - is that the case? It seems to be doing it in my case.
I've got a maven generated web service client with all the policy and WSDL data included in the jar file, but creation of the service client proxy is still very slow (a few seconds, which for a short-running command-line tool seems like forever). Is there some trick to get the initialization time down?
|
|
|
|
|
|
|
Re: Metro initialization performance
Posted:
Jul 14, 2009 10:06 AM
in response to: jvrobert
|
|
|
There are a few things that can cause slowness in JAX-* technologies. specifically instantiating the JAXBContext is a really lengthy process. The WSDL, if you want, can be copied locally to your WEB-INF/wsdl folder, or into your JAR. The client needs to reference that in its WebService annotation. But the recommended approach is to point it to the web WSDL, as you state that you are already doing. Does JAX-WS cache the WSDL it downloads at all? (are secondary transactions faster)
|
|
|
|
|
java.net RSS
