WTPNewsletter 20071019

WTP Weekly What's Cooking?

Headline News!

• WTP 2.0.2 bi-weekly M build declared today.
• WTP 3.0 M3 weekly I build declared today.

WTP 2.0.2

October 12, 2007 - October 19, 2007

• Smoketest Results

• 2.0.2 Bugs fixed this week

• 2.0.2 Remaining Targeted Defects

• All Remaining 2.0.2 Targeted Enhancements

• Plug-in Version Information

Versioning Report

WTP 3.0

October 12, 2007 - October 19, 2007

• Bugzilla 206957 found, potentially a bad bug and still needs investigation.

• Smoketest Results

• 3.0 Bugs fixed this week

• 3.0 Enhancements added this week

• Build Notes

• 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