Jump to: navigation, search

WTPNewsletter 20080303

Revision as of 14:00, 3 March 2008 by Hjzhang.ca.ibm.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

WTP Weekly What's Cooking?

Headline News!


WTP 2.0.2

February 18, 2008 - March 03, 2008

2.0.2 Release Page

  • Plug-in Version Information
Versioning Report


WTP 3.0

February 18, 2008 - March 03, 2008

  • Changes this week
The line delimiter preferences have been removed from the XML, HTML, JSP, and CSS preference pages to eliminate redundancy and confusion. Users may still set a workspace-wide default using the Workspace preference page or change existing resources with the File->"Convert Line Delimiters To" menu. Files will retain their line delimiters when they are edited.


  • Plugin Version Information
Version Info

References

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