Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334706 - Web Service Wizard: Error Template has not been defined
Summary: Web Service Wizard: Error Template has not been defined
Status: RESOLVED FIXED
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: jst.ws (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: 3.2.3   Edit
Assignee: Mark Hutchinson CLA
QA Contact: Keith Chong CLA
URL:
Whiteboard: PMC_approved
Keywords:
Depends on:
Blocks: 334811
  Show dependency tree
 
Reported: 2011-01-18 16:03 EST by Mark Hutchinson CLA
Modified: 2011-01-27 13:05 EST (History)
1 user (show)

See Also:
david_williams: pmc_approved+
keith.chong.ca: pmc_approved? (raghunathan.srinivasan)
keith.chong.ca: pmc_approved? (naci.dai)
keith.chong.ca: pmc_approved? (deboer)
keith.chong.ca: pmc_approved? (neil.hauge)
keith.chong.ca: pmc_approved? (kaloyan)
keith.chong.ca: review+

Attachments
proposed patch (2.25 KB, patch)
2011-01-18 16:16 EST, Mark Hutchinson CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Hutchinson CLA 2011-01-18 16:03:12 EST 
To reproduce:
1. Create an EJB Project named "WebServiceProjectClient"
2. Add a WSDL file to this EJB project.
3. Right click on the WSDL and select "Web Services > Generate Java Bean Skeleton"

Notice this excpetion


IWAB0234E An internal error occurred. Details: Template  has not been defined.
    java.lang.IllegalArgumentException: Template  has not been defined.
    at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl.getTemplate(FacetedProjectFrameworkImpl.java:569)
    at org.eclipse.wst.common.project.facet.core.ProjectFacetsManager.getTemplate(ProjectFacetsManager.java:268)
    at org.eclipse.jst.ws.internal.consumption.ui.wsrt.WebServiceRuntimeExtensionUtils2.doesClientRuntimeSupportTemplate(WebServiceRuntimeExtensionUtils2.java:1832)
    at org.eclipse.jst.ws.internal.consumption.ui.wsrt.WebServiceRuntimeExtensionUtils2.getClientRuntimeId(WebServiceRuntimeExtensionUtils2.java:1349)
    at org.eclipse.jst.ws.internal.consumption.ui.widgets.runtime.ClientRuntimeSelectionWidgetDefaultingCommand.defaultClientSideFromServiceSide(ClientRuntimeSelectionWidgetDefaultingCommand.java:1317)
    at org.eclipse.jst.ws.internal.creation.ui.widgets.runtime.ServerRuntimeSelectionWidgetDefaultingCommand.defaultClientSide(ServerRuntimeSelectionWidgetDefaultingCommand.java:248)
    at org.eclipse.jst.ws.internal.creation.ui.widgets.runtime.ServerRuntimeSelectionWidgetDefaultingCommand.execute(ServerRuntimeSelectionWidgetDefaultingCommand.java:216)
    at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
    at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
    at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
Comment 1 Mark Hutchinson CLA 2011-01-18 16:16:04 EST 
Created attachment 187047 [details]
proposed patch
Comment 2 Mark Hutchinson CLA 2011-01-18 16:36:19 EST 
    * Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. 

If certain projects are in the workspace the Web Services wizard will not launch.  Users are blocked from creating web services.

    * Is there a work-around? If so, why do you believe the work-around is insufficient? 

Users can rename the project called "WebServiceProjectClient" to something different.

    * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? 

This has been manually tested.

    * Give a brief technical overview. Who has reviewed this fix?

We were passing in the name of the service project into WebServiceRuntimeExtensionUtils2.getClientRuntimeId instead of the client project. 

Keith will review the fix.


    * What is the risk associated with this fix? 
Very low.
Comment 3 Keith Chong CLA 2011-01-18 17:28:45 EST 
Looks good Mark. Thanks.
Comment 4 Keith Chong CLA 2011-01-18 17:42:32 EST 
PMC, please review/approve.
Comment 5 Mark Hutchinson CLA 2011-01-19 11:42:51 EST 
Checked into R3_2_maintenance