Revision as of 00:46, 8 April 2008 by Hjzhang.ca.ibm.com
WTP Weekly What's Cooking?
March 31, 2008 - April 07, 2008
- WTP 3.0 M6 Milestone build S-3.0M6-20080404175400
- New Help for Old Friends III (Note the large number of removed resources in J2EE)
- Plugin Version Information
- Noteworthy mailing list posts
- Information on P2
- JSF Tools Plugins: Incrementing minor version
- Changes to Web services tools in M6
- Changes in version number for command.env.ui and wst.ws plugin
- New versions for Validation Framework plug-ins
- New versions for Faceted Project Framework plugins
- Platform fix for displaying proper resource icons in the navigator/project explorer
- Server plugin version changes - next week
- DependencyGraphManager Job changes
- Server tools job changes
- New features in Faceted Project Framework
- Dali naming convention for getter methods
Previous Adopter Breakage Report Information
- 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.