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 20070330
Contents
WTP Weekly What's Cooking?
Headline News!
- WTP 2.0 Now Featuring JSF and JPA Tooling!
- This week's WTP SDK and runtime zips now include the JSF and JPA projects.
- Note that JPA uses bugzilla target 1.0 for the bugzilla release and JPA is aligned with WTP proper.
- WTP 2.0 Feature Versions Updated!
- The feature versions for WST,JST, and JSF were all updated to 2.0.0
- The feature versions for JPA were updated to 1.0.0
- WTP 2.0 Deprecated Plugins Removed!
- org.eclipse.wst.internet.proxy
- org.eclipse.wst.internet.proxy.infopop
- See Bug 175171 for details
WTP 2.0
- Remaining Europa Timeline
March 2007 - June 2007 Platform +1 WTP M6 - API Freeze Mar 23 Mar 30 Apr 06 M7 - RC0 May 04 May 11 May 18 RCn... Europa Jun 29 Jun 29 Jun 29
March 23, 2007 - March 30, 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 Changes
Remaining for 2.0 M6
Migrating to M6
- See the M6 Migration Guide for help porting to M6
Focus Areas
WTP 1.5.4
March 23, 2007 - March 30, 2007
- Plugin Version Changes
Remaining for 1.5.4