Bug 216345 - Class can't be found error when starting a bujava scenario with a java project
Summary: Class can't be found error when starting a bujava scenario with a java project
Status: CLOSED FIXED
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: jst.ws (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M5   Edit
Assignee: jst.ws CLA
QA Contact: Kathy Chan CLA
URL:
Whiteboard:
Keywords: contributed
Depends on:
Blocks:
 
Reported: 2008-01-23 16:25 EST by Gilbert Andrews CLA
Modified: 2008-06-11 16:20 EDT (History)
0 users

See Also:


Attachments
this patch improves the way force classpath is done (2.38 KB, patch)
2008-01-23 16:31 EST, Gilbert Andrews CLA
bjorn.freeman-benson: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gilbert Andrews CLA 2008-01-23 16:25:11 EST
Build ID: 0109

Steps To Reproduce:
1.Create a java project put a bean in the source file
2.Create a web project
3.Right click on the bean and select create a webservice. 
4.Make sure the webproject you created is chosen on the first page 
5.Hit finsih you will get an error and you can go no further in the wizard.


More information:
This problem is appearing because the force update classpath is running while we are trying to access the classpath.
Comment 1 Gilbert Andrews CLA 2008-01-23 16:31:07 EST
Created attachment 87703 [details]
this patch improves the way force classpath is done

There are two changes that have been made to the code. The force classpath was being called twice when it only needed to be called once. This is a performance issue and Ive corrected it. 

Ive also added the force classpath method to be run as a job and we do not move past the job until it is finished in this way we do not try and access this resaource when it isnt ready.
Comment 2 Kathy Chan CLA 2008-01-23 23:18:08 EST
Patch reviewed and committed.  Would this affect the other streams (R1_5_maintenance and R2_0_maintenance) as well?

Patch released to HEAD as v200801240414.
Comment 3 Kathy Chan CLA 2008-01-30 14:19:15 EST
Gil just confirms that this problem does not appear on WTP 1.5.5 and WTP 2.0.2, so the fix is only required in HEAD and does not need to be backported to the maintenance releases.
Comment 4 Kathy Chan CLA 2008-02-28 14:10:55 EST
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!

Comment 5 David Williams CLA 2008-04-24 00:43:55 EDT
mass change to add 'contributed' keyword based on bugzilla query, please correct if that's not accurate (by marking patches as obsolete and removing the 'contributed' keyword. 
Comment 6 Kathy Chan CLA 2008-06-11 16:20:26 EDT
Bug cleanup.  Closing on behalf of the originator.