Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318976 - In org.eclipse.wst.wsdl, bundle dependency on javax.wsdl needs to be updated
Summary: In org.eclipse.wst.wsdl, bundle dependency on javax.wsdl needs to be updated
Status: CLOSED DUPLICATE of bug 265772
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: wst.wsdl (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: wst.wsdl CLA
QA Contact: Valentin Baciu CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-06 04:53 EDT by Gerald Preissler CLA
Modified: 2010-07-06 10:08 EDT (History)
1 user (show)

See Also:

Attachments
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 Gerald Preissler CLA 2010-07-06 04:53:24 EDT 
In Helios, javax.wsdl is delivered in versions 1.5.1 and 1.6.2. org.eclipse.wst.wsdl declares a bundle dependency javax.wsdl;bundle-version="[1.5.0, 1.6.0)". This leads to javax.wsdl_1.5.1 being used in all cases.

If the intention is to allow the use of the latest version of javax.wsdl_1.6 it would be nice if the dependency could be updated. We have a couple of components that depend on 1.6, and we're running into classloading issues otherwise when interacting with the wsdl model.
Comment 1 Valentin Baciu CLA 2010-07-06 10:08:34 EDT 
Hi Gerald, the dependency range that limits the WSDL EMF model and the majority of WTP components (except JAX-WS) to use javax.wsdl 1.5.1 is intentional.

The upgrade is typically a bit more involved than simply changing the version range given that the JWSDL / WSDL4J have in the past changed APIs between releases. See bug 197197, bug 252257 and bug 252258 for the previous effort to upgrade from 1.4 to 1.5.1.

We have a number of enhancements open to track the need to upgrade to 1.6.2. See bug 265772 and bug 265773. I will mark this bug as a duplicate of bug 265772.

*** This bug has been marked as a duplicate of bug 265772 ***