early draft for example already out of date, but thanks to Jens for getting it started)

WST Core Plugins

The core of the WST consists of the following modules:

• the structured source editing (sse) framework: provides a base (a model (core) and a editor (ui)) for all web artifact specific implementations
• the validation framework: in the initial CVS structure there is only the interface to this framework included
• utility modules:
  • URI resolving: a framework for resolving URIs with a XML specific implementation using a catalog of schemas
  • encoding: a framework for determining the encoding of a resource using the information in the header and the file encoding
  • content model: provides a sse independent model of a web artifact
  • ui utility classes: has support for drag'n'drop, actions and wizards

Plugin Descriptions

org.eclipse.wst.contentmodel

This plugin provides a contentmodel of the documents which can be used without the structured source editor. Right now there exist two refinements of this plugin: a dtd and a xsd contenmodel.

org.eclipse.wst.encoding

A general purpose framework for determining the encoding of a resource using specific header information (e.g. <?xml encoding) and file encoding.

org.eclipse.wst.sse.core

The core model of the sse framework. It provides the base document classes, builders and parsers.

org.eclipse.wst.sse.ui

The base editor of the sse framework. It provides the hooks for content assist, breakpoints, debugging, open-on, quickfix, spell checking and a content outline.

org.eclipse.wst.ui

UI Utility classes for actions, drag'n'drop and wizards.

org.eclipse.wst.uriresolver

API for an URI resolver.

org.eclipse.wst.validation.core

The interface to the validation framework.

org.eclipse.wst.xml.uriresolver

An implementation of the URI resolver specification. Uses a XML catalog to resolve URIs.

org.eclipse.wst.xml.uriresolver.ui

The UI (preference pages) for the XML URI resolver implementation.