Jump to: navigation, search

Difference between revisions of "WTPNewsletter 20080218"

Line 28: Line 28:
=== February 11, 2008 - February 18, 2008 ===
=== February 11, 2008 - February 18, 2008 ===
*WTP 3.0 M5 [http://download.eclipse.org/webtools/downloads/drops/R3.0/S-3.0M5-20080218021547/ S-3.0M5-20080218021547]
*WTP 3.0 M5 [http://www.eclipse.org/webtools/development/news/3.0M5/main.php New and Noteworthy]
*[http://wiki.eclipse.org/WTP_Functional_Test_R30_M5 Test Results]
*[http://wiki.eclipse.org/WTP_Functional_Test_R30_M5 Test Results]

Latest revision as of 12:33, 19 February 2008

WTP Weekly What's Cooking?

Headline News!

WTP 2.0.2

February 11, 2008 - February 18, 2008

  • Plug-in Version Information
Versioning Report

WTP 3.0

February 11, 2008 - February 18, 2008

  • Plugin Version Information
Version Info


Previous Adopter Breakage Report Information

  • 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.

Back to What's Cooking Archive

Back to Web Tools Project Wiki Home