WTPNewsletter 20070615

From Eclipsepedia

Revision as of 15:48, 15 June 2007 by Jlanuti.us.ibm.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

WTP Weekly What's Cooking?

Headline News!

  • First declared 1.5.5 M build June 15th.
  • RC3 declared June 15th.
  • Breaking change was introduced in JSF, the following classes were removed:
Plugin : org.eclipse.jst.jsf.common, Class : org.eclipse.jst.jsf.common.metadata.internal.MetaDataModelContextImpl, Class : org.eclipse.jst.jsf.common.metadata.query.MetaDataQueryHelper
See 188723 for more details.


WTP 2.0

June 2007
Platform +1 WTP
RC4 June 15 June 20 June 21
Europa GA June 29 June 29 June 29


June 08, 2007 - June 15, 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
Version Info


Remaining for 2.0 RC4


Focus Areas


WTP 1.5.5

June 08, 2007 - June 15, 2007

  • Plugin Version Changes
Versioning Information


References



Back to What's Cooking Archive

Back to Web Tools Project Wiki Home