Skip to main content

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.

Jump to: navigation, search

WTPNewsletter 20070420

WTP Weekly What's Cooking?

Headline News!

  • Visit the WTP 2.0 Ramp Down plan for updated information on features still in plan for 2.0.
  • JSF restructuring in progress - see bug 181822 for details or to add comments.
  • BEA Generic Server Adaptors removed from WTP builds. They can be downloaded from BEA on other servers option.
  • WTP 1.5.4 RC declared. Release scheduled for May, 4th.
  • JEM is now packaged as a part of WST in the WTP SDK and runtime zips for 1.5.4.

WTP 2.0

  • Remaining Europa Timeline
April 2007 - June 2007
Platform +1 WTP
M7 - RC0 May 04 May 11 May 18
RCn...
Europa Jun 29 Jun 29 Jun 29


April 13, 2007 - April 20, 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
Version Info


Remaining for 2.0 RC0

Migrating to M6

Focus Areas


WTP 1.5.4

April 13, 2007 - April 20, 2007

  • Plugin Version Changes
Versioning Information

Remaining for 1.5.4


References

Back to What's Cooking Archive

Back to Web Tools Project Wiki Home

Back to the top