Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
WTPNewsletter 20070608
Contents
WTP Weekly What's Cooking?
Headline News!
- RC2 declared June 6th.
- Breaking change was introduced in RC2 around EARImport, more details here.
- RC3 "weekly" build declared.
- In RC3, there are changes to JSF features. The JSF features will go away and be a part of JST, except for the web page editor piece, that will become its own feature.
- In RC3, there were also XML/XSD feature changes.
WTP 2.0
May 2007 - June 2007 Platform +1 WTP RC3 June 08 June 13 June 14 RC4 June 15 June 20 June 21 Europa GA June 29 June 29 June 29
June 01, 2007 - June 08, 2007
- Adopter Breakage Report
- Report
- Details
- In org.eclipse.wst.server.ui.internal.Messages, the fields host,name,vendor, and version were removed.
- In the internal package, org.eclipse.wst.server.core.internal, deprecated classes ModuleEvent, ModuleFactoryEvent, and IModuleListener were removed.
- In the internal class org.eclipse.wst.server.core.internal.ServerPlugin, getModuleArtifact(...) was removed.
- In the internal class, org.eclipse.jst.j2ee.internal.common.operations.JavaModelUtil, the method findType(..) changed arguments. This class is basically a copy of a JEM class to avoid adding a JEM dependency, and to keep up with changes in JEM, this class was updated.
- In org.eclipse.wst.wsdl.binding.soap.SOAPHeader and org.eclipse.wst.wsdl.binding.soap.SOAPHeaderFault, the methods getPart(...), setPart(...), getMessage(...), setMessage(...) were replaced by new methods. Details:
- The WSDL model SOAPHeader and SOAPAddress classes should have been inheriting the WSDL4J interfaces but weren't. Unfortunately the javax.wsdl interface already defines getMessage() and getPart () using a different signature. So this is a case where in order to 'fix' our model to make it comply with the WSDL4J we needed to break the 'provisional API' (these classes specified api=false in the component.xml file). Current clients will simply need to change references from getPart or getMessage to getEPart and getEMessage to access the EMF equivalent classes.
- Plugin Version Information
Remaining for 2.0 RC3
Focus Areas
WTP 1.5.5
Just starting builds. Declared maintenance build targeted for next Friday.
June 01, 2007 - June 08, 2007
- Plugin Version Changes
References
- Visit the WTP 2.0 Ramp Down plan for updated information on WTP 2.0.