Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 185198 - some plugins should move to javax.wsdl pre-req
Summary: some plugins should move to javax.wsdl pre-req
Status: CLOSED DUPLICATE of bug 197197
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: wst.wsdl (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Valentin Baciu CLA
QA Contact: Craig Salter CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-02 14:55 EDT by David Williams CLA
Modified: 2007-10-02 10:24 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 David Williams CLA 2007-05-02 14:55:00 EDT 
In moving Axis to Orbit, we "split out" jars which had previously been nested (and effectively hidden). One of those was wsdl4j-1.5.1.jar, which, following the "best practice" naming conventions of Orbit, translates to the javax.wsdl bundle version 1.5.1. 

I've recently learned we already had a version, 1.4, of javax.wsdl, in a bundle called org.wsdl4j. (which is still only in WTP, not in Orbit). 

While in theory, we might get away with having two versions of the javax.wsdl packages in WTP, seems likely to cause problems or, at least, confusion. 

Therefore, since axis 1.4 requires javax.wsdl 1.5.1, I think it is best that all plugins that currently pre-req org.wsdl4j, change to pre-req javax.wsdl 1.5.1. 

This will obviously take some testing effort to be sure all works well with this upgrade.
Comment 1 Valentin Baciu CLA 2007-09-15 21:32:00 EDT 
I'm marking as a duplicate of bug 197197 since both bugs appear to request the same thing. There's also bug 103504 which is asking for going all the way to 1.6.*, as that is the latest WSDL4J version. As I describe in there, the complicating factor is that the WSDL EMF model implements the JWSDL APIs. The changes could be quite disruptive to downstream clients.

*** This bug has been marked as a duplicate of bug 197197 ***
Comment 2 Valentin Baciu CLA 2007-10-02 10:24:43 EDT 
Closing. Please re-open if you disagree with comment #1.