Community
Participate
Working Groups
1. Create EJB 3.0 with unsupported Web service runtime 2. Web Service wizard will default incorrect initial project which will cause exception instead of giving out error in the first page.
Created attachment 108771 [details] Here's the patch. Attaching the patch.
The patch only affect bottom-up EJB Web service scenarios. EJB 2.0, 2.1 and 3.0 has been tested.
Changes are in org.eclipse.jst.ws.internal.creation.ui.widgets.runtime.ServerRuntimeSelectionWidgetDefaultingCommand line 145. Where the initialProject_ need to set in DefaultRuntimeTriplet for bottom-up EJB Web service scenarios. If the initialProject_ (where contains the EJB class) isn't set, the wizard would have problem to locate the EJB later in the Bean Identify page where it will give the exception.
I've reviewed the code with Allan. The change is only affecting bottom-up EJB scenario (bottom-up Java, skeleton and client project defaulting is not touched). So with the fix, rather than defaulting to a project not containing the EJB and causing error down the road in the wizard, we are defaulting the project to the initial project for bottom-up EJB if the normal defaulting logic could not reasonably default a project. After the defaulting code is done, the validation code would be run to catch any error with using that project in the chosen scenario. This is better than the original problem where it silently pick another project fails later on. Allan has tested all EJB scenarios and Java scenarios as well. PMC, please approve for WTP 3.0.1.
Minor change, approved.
The patch for this defect has been committed and released to the HEAD and V301 streams under v200807302056.
This defect has been in resolve state for a while. Please verify this with the appropriate WTP driver which can be found in: http://download.eclipse.org/webtools/downloads/ We would verify and close the defect on the originator's behalf if it has not been verified 2 weeks after it's been changed to Verified state.
Verified
Closed
