| Summary: | WS Client Generation - Application and Utility Clients added to multiple EARs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | Ivan Castro <ivanc> | ||||
| Component: | jst.ws | Assignee: | Keith Chong <keith.chong.ca> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Keith Chong <keith.chong.ca> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | mahutch | ||||
| Version: | 3.2.2 | ||||||
| Target Milestone: | 3.5 M4 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ivan Castro
Created attachment 180371 [details]
Source patch for suggested fix
I'm attaching a patch that fixes this problem.
The fix looks good. Here's another way to describe the problem: When generating a Web service client into an Application Client, after finishing with the wizard, the project will be associated to any existent EAR in the workspace. It will also be associated with the EAR as specified in the wizard. When generating a Web service client into a Java Utility project, after finishing with the wizard, the project will be associated to any existent EAR in the workspace. Delivered to 3.4.2 and 3.5. |