Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

WTPNewsletter 20070713

WTP Weekly What's Cooking?

Headline News!

  • WTP 1.5.5 M Build Declared today, July 13. The schedule was tweaked to produce RC1 one week earlier.
  • First WTP 2.0.1 M build scheduled for next week. 2.0.1 will be delivered September 28, 2007.
  • No WTP 3.0 M1 builds yet, design discussions and planning is under way.


WTP 3.0

July 06, 2007 - July 13, 2007

  • Adopter Breakage Report
  • Report
  • Details
  • org.eclipse.jst.jsf.context.resolver.structureddocument.internal.impl.MetadataContextResolver was renamed to org.eclipse.jst.jsf.common.metadata.query.TaglibDomainMetaDataQueryHelper.
  • 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
Version Info


WTP 2.0.1

July 06, 2007 - July 13, 2007


  • Plugin Version Information
Versioning Report


WTP 1.5.5

July 06, 2007 - July 13, 2007

  • Plugin Version Changes
Versioning Information


References


Back to What's Cooking Archive

Back to Web Tools Project Wiki Home

Back to the top