Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 242440

Summary: Add service definition extension point to locate workspace artifacts
Product: [WebTools] WTP Webservices Reporter: Kathy Chan <kathy>
Component: jst.wsAssignee: Yen Lu <yenlu>
Status: RESOLVED FIXED QA Contact: Keith Chong <keith.chong.ca>
Severity: enhancement    
Priority: P3 CC: arawlins, edwinc, keith.chong.ca, yenlu
Version: 3.0Keywords: plan
Target Milestone: 3.1 M6   
Hardware: PC   
OS: Windows XP   
Whiteboard: extensibility
Attachments:
Description Flags
patch
none
Patch
none
Patch none

Description Kathy Chan CLA 2008-07-29 13:47:53 EDT 
The wsdl2java tools (called by the Web services wizard) are not honoring org.eclipse.wst.common.uriresolver.resolverExtensions point extensions, so creation of web service skeleton or a client using new web service wizard fails due to inability of resolution mechanism to resolve WSDL or XSD imports by not searching dependent projects.

Ideally, all web services tools (new web service wizard, new client wizard, web services explorer), and entry points to 3rd party tools (wsdl2java) should honor and utilize existing pluggable resolution mechanism.

A seperate RFE (bug 242406) has been opened to request for the support for the "wksp:" protocol.

When that RFE is implemented, a workspace resource input to wsdl2java should be wrapped in the wksp: URL, somewhere between web service wizard and wsdl2java invocation, so the control over resolution is within product, not 3rd party wsdl2java.
Comment 1 Kathy Chan CLA 2009-01-26 16:27:57 EST 
Instead of supporting wksp: protocol as originally requested, we proposed put in a new "service definition locator" extension point in WTP to look for extensions of how to look up WSDL/XSD files.  Then in the adopter product, a new extension to this new "service definition locator" extension could be put together to feed the "wksp: <some workspace file URL>" URL to the Web services wizard when a user select a workspace file and choose to run the Web services wizard.  Then with this new extension and the wksp protocol URL handler in the adopter product, the top-down and client Web services wizard would be aware of this new way of resolving files.
Comment 2 Yen Lu CLA 2009-01-26 16:33:45 EST 
It is not just the Web service wizards that need to respect the new extension point. The Web Services Explorer can also be launched with a WSDL in the workspace and can also grab URLs based on workspace entities.
Comment 3 Keith Chong CLA 2009-02-04 10:38:14 EST 
Hi Valentin, this one is mine.
Comment 4 Kathy Chan CLA 2009-02-11 22:44:38 EST 
Add a new service definition extension point so that extenders can provide a way to locate workspace artifacts.
Comment 5 Keith Chong CLA 2009-03-05 09:06:12 EST 
Yen, thanks for taking this. :-)
Comment 6 Yen Lu CLA 2009-03-08 17:47:29 EDT 
Created attachment 127970 [details]
patch
Comment 7 Yen Lu CLA 2009-03-10 14:28:38 EDT 
Created attachment 128241 [details]
Patch

Updated patch to account for adapter object changes.
Comment 8 Yen Lu CLA 2009-03-10 17:49:16 EDT 
Created attachment 128285 [details]
Patch

An updated patch to correct an indavertent NPE.
Comment 9 Keith Chong CLA 2009-03-11 14:38:12 EDT 
Fix released for 3.1 M6