| Summary: | Remove WSDL 1.4 | ||
|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | Keith Chong <keith.chong.ca> |
| Component: | wst.ws | Assignee: | Keith Chong <keith.chong.ca> |
| Status: | CLOSED FIXED | QA Contact: | Keith Chong <keith.chong.ca> |
| Severity: | normal | ||
| Priority: | P3 | CC: | bluesoldier, manderse, valentinbaciu |
| Version: | 3.1 | Keywords: | plan |
| Target Milestone: | 3.1 M6 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | Other | ||
|
Description
Keith Chong
Curious to know why it is being removed ? What is users with projects using this feature going to do going forward ? Hi Max, The main reason is that the WTP components all have moved up to WSDL 1.5, so WTP has no further use of this old version. Any adopters of WTP that still want to use 1.4 will have to adapt, so, for example, as a compile time dependency, they will have to obtain the package themselves. Note that the package is currently provided in the Orbit bundle, and is listed as a "handy extra" in the WTP 3.1 builds. Just to elaborate...once the plugin is removed from WTP, this orbit zip will not contain the plugin. You can still get it from the orbit download site. (In reply to comment #3) > Just to elaborate...once the plugin is removed from WTP, this orbit zip will > not contain the plugin. You can still get it from the orbit download site. Hi Keith, What do you mean "this orbit zip will not contain the plugin."? Will this plugin be removed from Orbit build along with wtp? Okey - so users can still develop 1.4 app features but it will just be done via WSDL 1.5 instead of 1.4 (just trying to understand if this is purely something that affect plugin dev's or also users that used the WSDL 1.4 based features) (In reply to comment #4) > (In reply to comment #3) > > Just to elaborate...once the plugin is removed from WTP, this orbit zip will > > not contain the plugin. You can still get it from the orbit download site. > Hi Keith, > What do you mean "this orbit zip will not contain the plugin."? > Will this plugin be removed from Orbit build along with wtp? My apologies, once the plugin is removed from the WTP _feature_, the WTP zip will not contain the plugin. You can still get the plugin from the orbit bundle/download site. (In reply to comment #5) > Okey - so users can still develop 1.4 app features but it will just be done via > WSDL 1.5 instead of 1.4 (just trying to understand if this is purely something > that affect plugin dev's or also users that used the WSDL 1.4 based features) Hi Max, I don't know how all dev's/adopters/users are using WSDL 1.4. There may be some sort of intervention required, or may be not. For example, one of my web projects already has the 1.4 jar physically located in the project and is on the web app library classpath. So this is one scenario where I may not have to do any migration. For plugin developers, future work should be done against 1.5. I'm not enough into how webservices tooling is implemented but I just want to be sure this does not have the same effect as if JDT decided to remove support for Java 1.4 (i.e. the projects I maintain that uses Java 1.4 wouldn't compile nor run in the java environment they were originally intended for). The feature change has been updated and released for 3.1 M6. Verified. The wtp and wtp-sdk zips do not contain the javax.wsdl_1.4.0 plugin. Closing bug. |