Bugzilla – Full Text Bug Listing
| Summary: | Cannot use Java project for BUJava | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | Yen Lu <yenlu> | ||||||||||||||||||||||||
| Component: | jst.ws | Assignee: | Gilbert Andrews <gilberta> | ||||||||||||||||||||||||
| Status: | CLOSED FIXED | QA Contact: | Kathy Chan <kathy> | ||||||||||||||||||||||||
| Severity: | major | ||||||||||||||||||||||||||
| Priority: | P3 | CC: | clin, david_williams | ||||||||||||||||||||||||
| Version: | 2.0 | ||||||||||||||||||||||||||
| Target Milestone: | 1.5.5 M155 | ||||||||||||||||||||||||||
| Hardware: | PC | ||||||||||||||||||||||||||
| OS: | Windows XP | ||||||||||||||||||||||||||
| Whiteboard: | 155patchCreated | ||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||
|
Description
Yen Lu
Yen, Just want to clarify the scenario. When you choose to create Web service on a Java bean on the Java project, the Web service wizard would choose a Web project in the workspace or propose to create a new Web project (since bottom-up Web service only support Web project, not Java project). Then the wizard would issue the error "the class X cannot be loaded via project Y". Are you proposing then the solution is the following: - The Web service runtime would allow the creation of Web service on Java project. When a Java project is choosen, the wizard would then silently create a Web project, generate the Web service there and add a J2EE module dependency to the Java project. Kathy, Yes. That is my proposal. This particular module dependency is not really a J2EE module dependency. It configures some project metadata so that when the application is deployed, the class contents of the Java project get bundled into either WEB-INF/classes or WEB-INF/lib of the Web project. This enables the solution for non-J2EE Web Services technologies (i.e. Axis) as well. Hi Gil, This would be similar to the add module dependency you already have for adding a Java project as a dependency to a Web project containing the sample JSP code. Created attachment 84451 [details]
consumption
Created attachment 84452 [details]
creation
Changing severity to Major since the wizard create the Web project for the user when they started off with Java project, so the user would expect the scenario to be one that is supported and is supposed to work. Created attachment 84671 [details]
fixes the ear creation problem
Created attachment 85089 [details]
corrections after Kathys review
Created attachment 85138 [details]
Modified patch
Adding a default constructor to AddModuleDependencyCommand so that we don't have to pass in TestInfo. Remove the call to addBuildPath which does not seemed to be necessary.
This latest patch has been tested with: 1. Starting with Java project, create bottom-up Web service with no Web project or EAR in workspace. 2. Starting with Java project, create bottom-up Web service by selecting to create a new Web project and EAR. 3. Starting with Java project, create bottom-up Web service by selecting to create into an existing Web project and EAR. 4. Starting with Java project, create bottom-up Web service and also creating client into Java Utility project and then selecting test to create a seperate sample project. This patch is ready to go into the WTP 1.5.5 patch stream. Created attachment 85140 [details]
consumption.ui patched JAR
Created attachment 85141 [details]
creation.ui patched JAR
I've attached the exported JAR for the 2 plugins that were changed for this defect. I've also tested the normal scenario of creating bottom-up Web service in a Web project and that's fine as well. Patch created in http://download.eclipse.org/webtools/patches/drops/R1.5/P-P20071218083716-20071218083716/ Be sure to carry forward to 2.0 and 3.0 streams if not done yet. The patch is assumed cumulative with all other patches created for 155. Created attachment 85484 [details]
wtp 30 patch
I've tested the WTP 1.5.5 patch in: http://download.eclipse.org/webtools/patches/drops/R1.5/P-P20071218083716-20071218083716/ I verified that the patch contains the fix for creating Web service starting with Java project. Yes, we will forward porting this fix into WTP 3.0 and WTP 2.0.2. Patch review and tested. It has been committed to HEAD and released as v200712182235. We still have to commit and test this in R2_0_maintenance. Created attachment 85688 [details] Delta patch on top of R1_5_5_patch This patch should be applied to the original patch that had been checked into R1_5_5_patch branch. It fixes the regression problem as reported on bug 213640. re-opening till new fix applied. The fixed fix is available at http://download.eclipse.org/webtools/patches/drops/R1.5/P-P20071221001459-20071221001459/ Created attachment 85719 [details]
New delta patch that fixes timing problem with classpath update
This patch in on top of the latest patch on R1_5_5_patches stream. It forces a classpath update to ensure that the J2EE module dependency is properly setup before we try to access the bean.
David, please get a new WTP 1.5.5 patch done containing this fix. Thanks! Latest patch has been built into patch builds >= P-P20071221174739-20071221174739 Created attachment 85747 [details]
Patch for R2_0_maintenance branch containing all the above patches
This patch has been committed and released to R2_0_maintenance.
Please verify the defect you originated with a recent WTP driver which could be found in: http://download.eclipse.org/webtools/downloads/ If defects in resolved state is not verified within a couple of weeks, the development team might verify and close the defect on the originator's behalf. Thank you for your attention! Verified in adoptor product. |