-
1. From wsdl to java and opposite to deployable service
asoldano Feb 8, 2011 4:01 AM (in response to jonny69)JBossWS comes with JAXWS tools for doing code-first and contract-first development, see http://community.jboss.org/wiki/JBossWS-JAX-WSTools
The wsdl you find in server/myserver/data/wsdl is the actual wsdl the server is using, as per JSR109 requirements. However, you can provide your own wsdl within the deployment and reference it in the @WebService annotation, see JAXWS spec / documentation.
Finally, consider having a look at the JBoss Tools project, as that offers Eclipse facilities for using the jbossws tools (the axis based stuff is not good at all with jbossws).
-
2. Re: From wsdl to java and opposite to deployable service
jonny69 Feb 8, 2011 2:32 PM (in response to asoldano)Hi Alessio!
Thanks for interesting my issue and the tutorial about JBossWs-Jax-WSTools.
According to that stuff,
JBossWS - JAX-WS Tools
The wsdl you find in server/myserver/data/wsdl is the actual wsdl the server is using, as per JSR109 requirements. However, you can provide your own wsdl within the deployment and reference it in the @WebService annotation, see JAXWS spec / documentation.
I know about it, but if I often change client-side, for example some changing in request parameter in Webservice methods, it influences on wsdl so in each time I should change my wsdl if I use wsdlLocation param in @Webservice annotation. So leaving server generate wsdl file is very comfortable.
I hope you undersand my problem. And the real issue is: get the most similar or exaclty the same server-side of WebService based od wsdl file.
Besides, thanks for your tips