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.
WTPNewsletter 20080324
Contents
WTP Weekly What's Cooking?
Headline News!
- WTP 3.0 M6 weekly I build I20080321174820
WTP 3.0
March 18, 2008 - March 24, 2008
- Please note that this build is based on the 0305-1100 platform build. There will be issues with using a later platform build with p2 enabled. For information on p2
- WTP 3.0 M6 weekly I build I20080321174820
- Plugin Version Information
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.