Bug 256676

Summary: AXIS WS runtime- specify root WSDL folder in Web service & client wizards & ANT tasks
Product: [WebTools] WTP Webservices Reporter: Eric Peters <ericdp>
Component: jst.wsAssignee: Eric Peters <ericdp>
Status: NEW --- QA Contact: Keith Chong <keith.chong.ca>
Severity: enhancement    
Priority: P3 CC: keith.chong.ca
Version: 3.0.3Keywords: helpwanted
Target Milestone: Future   
Hardware: PC   
OS: Windows XP   
Whiteboard: EaseOfUse

Description Eric Peters CLA 2008-11-26 12:30:14 EST
Build ID: WTP_R-3.0.3-20081113203138

Steps To Reproduce:
WSDL and XSD are always saved to WEB-INF/wsdl upon web service client generation. It is impossible to specify name or location of the wsdl.

If user is developing a client application with two web services. The user can place the WSDL and XSD files of the web service provider of each service in directories as per below:

WebContent
|
+----WEB-INF
|
+-----wsdl
|
+---CarSpec
| |
| +---findCarSpecInfoWS.wsdl
| |
| +---aaa.xsd
|
+---Customer
|
+---findCustomerInfoWS.wsd
|
+---aaa.xsd

Each WSDL file has an XSD file (e.g. aaa.xsd) that is read in using schemaLocation. When a web service client is generated for each web service the XSD and WSDL files are generated in the WEB-INF/wsdl directory. When the second web service client is generated, however, it overwrites the XSD file generated by the first web service client, because the names of the XSD files happen to be the same name. (So to avoid this problem the user has to organise their projects in separate directories.)



More information:
Expectation is that when using the web service client wizard, it is possible to specify the directory where wsdl is. This should also be possible via ANT tasks.
Comment 1 Kathy Chan CLA 2009-02-11 22:36:18 EST
Considering for WTP 3.1.  Note that since this involve UI changes, the latest this can go in for WTP 3.1 is M6.
Comment 2 Eric Peters CLA 2009-02-26 20:54:10 EST
*** Bug 255803 has been marked as a duplicate of this bug. ***
Comment 3 Eric Peters CLA 2009-02-26 20:54:30 EST
*** Bug 255787 has been marked as a duplicate of this bug. ***
Comment 4 Keith Chong CLA 2009-10-08 10:23:45 EDT
This is not in the 3.2 plan.