Community
Participate
Working Groups
If the a webservice file is using a uppercase for the extension .WSDL then the Web Service Client wizard does not find the resource Steps to reproduce: Create a webservice definition file with an uppercase Right click on the file and select Webservices > Generate Client Result: Service definition field is not populated. Browsing to find the file will not allow you to select the file located in the workspace. Workaround: Change the extension to lowercase .wdl
Additionally, there are a few places where .WSIL is not handled by the Web services tools.
Created attachment 98339 [details] Fixes .WSDL and .WSIL
Also fixed .XSD in one place in WSDLCopier
Problem: There are several areas in the Web service wizards that does not allow uppercase WSDL/WSIL files to be picked even though the files are valid (i.e. you can open a .WSDL file in the WSDL editor with no problem). Fix: The fix is to use equalsIgnoreCase() or toLower() as appropriate to ensure that the Web service wizards will tolerate WSDL/WSIL files. This fix is only needed for determine whether the selection is valid. Once we are able to select these files, the Web service tools itself actually already works for WSDL/WSIL files. Testing: I've tested our usual top-down, buttom-up, client scenarios and also the generate wsil scenario as well. Review: Kathy, please review this patch.
Patch looks good. Thanks Andrew! PMC, please approve for WTP 3.0 RC1.
Approved. Patch looks simple and it seems that the WS team is convinced that it should go in 3.0.
Patch committed and released to HEAD as v200805082126.
Verified on WTP 3.0 06/08.