Community
Participate
Working Groups
- The WSDL file of webservice providers whose WSDL file is located in a sub-folder of '/WEB-INF/wsdl' is dynamically generated at JAX-WS bootstrap instead of the existing WSDL file to be published. - Webservice consumer specific WSDL files might interfere with provider specific WSDL files, e.g. if defining same services or ports. In consequence, all webservice providers of that plugin are not published. - redundant WSDL file in webservice stub JAR-file.
06.01.2012 dwi Problem: a) The WSDL file of webservice providers whose WSDL file is located in a sub-folder of '/WEB-INF/wsdl' is dynamically generated at JAX-WS bootstrap instead of the existing WSDL file to be published. b) Webservice consumer specific WSDL files might interfere with provider specific WSDL files, e.g. if defining same services or ports. In consequence, all webservice providers of that plugin are not published. c) redundant WSDL file in webservice stub JAR-file. Solution: a) changed JAX-WS resource loading to also look in subfolders for existing resources b) WS provider specific WSDL files should be located in the folder '/WEB-INF/wsdl/provider' whereas consumer specific WSDL files in '/WEB-INF/wsdl/consumer'. In turn, JAX-WS is instrumented to ignore all the files in the (sub-)folder '/WEB-INF/wsdl/consumer' when publishing the endpoints. c) WSDL file is not put into the JAR archive anymore when building the webservice stub.
ticket will be closed after it's shipped with juno
ticket closed. deliverd as part of eclipse scout 3.8.0 (juno release train)
