Bugzilla – Full Text Bug Listing
| Summary: | New -> Web Service.. not seeing files from project on build path | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | Matt Carter <matt> | ||||
| Component: | wst.ws | Assignee: | Kathy Chan <kathy> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | Keywords: | Documentation | ||||
| Version: | 1.5 | ||||||
| Target Milestone: | 1.5 M5 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Matt Carter
Just assigning to more specific component based on abstract. Kathy, would you please try this on I20050422? Flexible project support may be handling this scenario now, or it may still be a problem, in which case we need to determine if this a bug in Web services tools or in J2EE tools and assign the bug / pursue a fix if at all possible in M4. This is a problem because the project build path is not set properly. See defect 90560 (which had been targetted to m5): https://bugs.eclipse.org/bugs/show_bug.cgi?id=90560 *** This bug has been marked as a duplicate of 90560 *** A fix is provided to set classpath passed to the Axis emitter properly even when: - a project depends on another project - a module depends on other module within the same project Please note that even with this fix, the wizard would completes successfully but the user would still have to manually add the dependent JARs to the module's WEB-INF/lib directory in order have the Web service to deploy and run properly. Fix committed. Note that we are using an internal J2EE API and would have to switch to use an external API once the J2EE team provides one. This work will be track under 90560. Created attachment 21232 [details]
JAR for org.eclipse.jst.ws.axis.consumption.ui
Changed Version field given new release numbering. Unable to verify on I2005 due to bug 103628; cannot create test Dynamic Web Project. https://bugs.eclipse.org/bugs/show_bug.cgi?id=103628 Also recently in I20050712 WST build, unable to complete Bottom-Up Web Service wizard due to exception (in clean project but with original class for which this bug was filed). Exception seems unrelated but prevents testing. Will reproduce on request. Please advise. I will re-attempt to verify as soon as above bug resolved. s/I2005 /I20050713-200507130840 / I have got the same problem (using WinNT and all the newest releases; fresh workspace): IWAB0398E Error in generating WSDL from Java If you are still getting the problem with the latest build, please re-open the defect with the exact steps to reproduce the problem (including the necessary files). I tried with Eclipse 3.1 and WTP0.7RC1. I was able to create dynamic Web project successfully (with either 1 module per project or multiple modules per project). I was able to run a bottom-up Web service creation scenario with project A depending on classes from project B. I did not run into the NoClassDefFound problem going through the wizard. This problem was specifically fixed on 05/16. Please note that you need to JAR up the classes in the dependent project B and add it to the WEB-INF/lib directory before running the bottom-up Web service scenario. Otherwise, you will get a Class Not Found exception in the server console when trying to deploy the Web service to Axis. You would still be able to go through the wizard cleanly even if you forgot to add the JAR to the lib directory though. This change is a bulk update of all _un_targeted, fixed, resolved bugs upon release of M5. This particular bug _might_ have been fixed earlier than M5. (Feel free to correct). As we are trying to close down WTP 1.5, please get the latest WTP 1.5 driver to verify the bug and reopen if the problem had not been fixed. If this defect is not verified/reopened by end of day 06/16, I'll attempt to verify the defect by reproducing the problem as described in the defect. However, since you know your scenario best, it would be more appropriate if you verify the fix. (In reply to comment #14) > As we are trying to close down WTP 1.5, please get the latest WTP 1.5 driver to > verify the bug and reopen if the problem had not been fixed. If this defect is > not verified/reopened by end of day 06/16, I'll attempt to verify the defect by > reproducing the problem as described in the defect. However, since you know > your scenario best, it would be more appropriate if you verify the fix. > Hi, I am still getting this error even while using WTP 1.5. Verified on behalf of submitter (Matt). This was fixed over a year ago, and has not resurfaced in WTP 1.5 or 1.5.1 to the best of our knowledge. Matt, if the problem recurs on WTP 1.5.1, please reopen. Thanks - CB. Closed. |