Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

WTP 2.0 API Delta

The following is a summary of the API changes between WTP 1.5 and 2.0: edit

Common Components

  • The ID value given for extensions to org.eclipse.wst.common.snippets.SnippetContributions can now be accessed programmatically

XML/JSP Components

  • Declared the org.eclipse.jst.jsp.core.tagsource Content Type for JSP 2.0 Simple Tag Extension files
  • org.eclipse.jst.jsp.core.taglib.ITaglibIndexListener and org.eclipse.jst.jsp.core.taglib.ITaglibIndexDelta are now API interfaces; the API versions have breaking changes from earlier unsupported revisions
  • The following hyperlinkDetectorTargets were set up, so adopters can target their hyperlink detectors to the xml, schema, wsdl, html, jsp editors via the org.eclipse.ui.workbench.texteditor.hyperlinkDetectors extension point: org.eclipse.core.runtime.xml, org.eclipse.wst.xsd.core.xsdsource, org.eclipse.wst.wsdl.wsdlsource, org.eclipse.wst.html.core.htmlsource, org.eclipse.jst.jsp.core.jspsource

Server Component

  • API support for external (non-workspace) modules added via org.eclipse.wst.server.core.IModule.isExternal() and associated methods in org.eclipse.wst.server.core.ServerBehaviourDelegate.
  • New API methods added to org.eclipse.wst.server.core.IServer including getLaunchConfiguration(), shouldPublish(), and shouldRestart().
  • Support for server scheduling rules added to org.eclipse.wst.server.core.ServerUtil.
  • Support for multiple artifacts in a single selection added via org.eclipse.wst.server.core.model.ModuleArtifactAdapterDelegate.getModuleArtifacts().
  • org.eclipse.wst.server.model.ModuleArtifactDelegate added as an abstract class (including additional support) for all artifact delegates.
  • Performance improvements added via new methods to org.eclipse.wst.server.core.model.ModuleFactoryDelegate.findModule() and getModule().
  • Support for better restarting added via org.eclipse.wst.server.core.model.ServerBehaviourDelegate.restartModule().
  • org.eclipse.wst.server.core.util.PublishUtil moved from jst.server and added to API.
  • Run on Server added to API via org.eclipse.wst.server.ui.actions.RunOnServerAction.
  • org.eclipse.wst.server.ui.ServerUIUtil provides additional methods to display new runtime and new server wizards.
  • org.eclipse.wst.server.ui.FacetRuntimeComponentLabelProvider provides a new facet runtime label provider.
  • Enhanced profiler support for TPTP in jst.server in provisional API.

WebServices and WSDL

  • The Web Services Explorer now supports a pluggable transport and message stack. A new extension point,, has been added to the Web Services Explorer. This extension point entry allows an extender to plug in a new factory for creating instances. The ISOAPTranport class is used by the Web Services Explorer for invoking Web services operations that uses the SOAP message protocol. The factory must implement the interface. Other supporting classes/interfaces which are part of this internal API can be found in the package.
  • A new optional attribute mergerClass is introduced in the Web services implementation type extension point This mergerClass should implement the newly defined interface which contains a load() and merge() method. This class is used for the purpose of Web services skeleton file merging for the Web service implementation type.
  • Adopters of the Web services creation framework can now use the same Web services pop-ups provided by the framework to process their custom types. They just need to provide an IAdapterFactory that adapts that custom type to IFile or String and register the factory with the Platform's AdapterManager (or extends the org.eclipse.core.runtime.adapters extension). There might be sematic changes post WTP 2.0 to change the type of object the custom types should be adapted to.



  • Application Configuration Resource File ("faces-config.xml") Model: Packages, org.eclipse.jst.jsf.facesconfig.*, provide programmatic access and manipulation of the standard JSF application configuration resource file (e.g. "faces-config.xml").
  • Design-Time Application Framework: Packages,org.eclipse.jst.jsf.core.designtime.*, simulates certain JSF runtime behavior (currently mainly EL variable/property resolution) at designtime and provides API for adopters to add the same for their custom extension of the JSF runtime (i.e. custom VariableResolver).
  • Model Context Framework: Packages, org.eclipse.jst.jsf.common.context, provides a generic way to describe specific instance contexts within an arbitrary model and derive orthogonal information about that context through related resolvers.
  • Packages, org.eclipse.jst.jsf.common.util, provides utility classes for manipulating JDT IType's, primarily as Java Beans.

JPT - Dali JPA Tools

  • None: No Public API's have been defined for this release due to the fact that our models are not quite at the correct level of maturity. The hope is that adopter feedback as a result of working with the release will allow us to harden the model and declare real API for future releases. See bug 178653 for more information.

Back to the top